Can´t get deploy working

[SaschaValentin]

Hello dear Caprover friends,

I have the feeling that I am completely incompetent when it comes to deploying apps. One-click apps and deploying via ImageName from Docker Hub work fine, but as soon as I have a Github repository, it doesn't work anymore. Specifically, it's about this one: https://github.com/SaschaValentin/noodlcloud

I have tried the first three variants of the dashboard. Here are the error messages:

Method 1:
„caprover deploy“

Message:
_Preparing deployment to CapRover...

You are not in a git root directory: this command will only deploy the current directory.
Run "caprover deploy --help" to know more deployment options... (e.g. tar file or image name)_

Method 2:
Upload a TAR to the Dashboard

In the build log:

_------------------------- Fri Feb 23 2024 07:30:43 GMT+0000 (Coordinated Universal Time)
Build started for noodlapp
Step 1/10 : FROM nikolaik/python-nodejs:python3.8-nodejs16

---> 30ad3ba2de0d
Step 2/10 : WORKDIR /usr/src/noodl-cloudservice

---> Using cache
---> 26fed00d92ab
Step 3/10 : COPY ./packages/noodl-cloudservice .

---> Using cache
---> 56ce1558c0b3
Step 4/10 : RUN npm install

---> Using cache
---> 101abe02a4c4
Step 5/10 : RUN npm run build

---> Using cache
---> 188790788943
Step 6/10 : WORKDIR /usr/src/app

---> Using cache
---> e9d576c70dcf
Step 7/10 : COPY packages/noodl-cloudservice-docker .

---> Using cache
---> 58e86d7f2311
Step 8/10 : RUN npm install --install-links

---> Using cache
---> c78e58295408
Step 9/10 : EXPOSE 3700

---> Using cache
---> c23e338d9f42
Step 10/10 : CMD [ "node", "./src/index.js" ]

---> Using cache
---> e8ee708904f6
Successfully built e8ee708904f6
Successfully tagged img-captain-noodlapp:latest
Build has finished successfully!_

But in the App log:

2024-02-23T07:35:25.936393505Z (node:1) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./public/" in the "exports" field module resolution of the package at /usr/src/app/node_modules/extract-files/package.json.
2024-02-23T07:35:25.936445312Z Update this package.json to use a subpath pattern like "./public/".
2024-02-23T07:35:25.936451615Z (Use node --trace-deprecation ... to show where the warning was created)
2024-02-23T07:35:25.937423700Z Noodl Parse Server listening at http://localhost:3000
2024-02-23T07:35:25.940676072Z winston-mongodb: error initialising logger MongoParseError: Invalid connection string
2024-02-23T07:35:25.940708446Z at parseConnectionString (/usr/src/app/node_modules/mongodb/lib/core/uri_parser.js:575:21)
2024-02-23T07:35:25.940718024Z at connect (/usr/src/app/node_modules/mongodb/lib/operations/connect.js:282:3)
2024-02-23T07:35:25.940724779Z at /usr/src/app/node_modules/mongodb/lib/mongo_client.js:260:5
2024-02-23T07:35:25.940728809Z at maybePromise (/usr/src/app/node_modules/mongodb/lib/utils.js:692:3)
2024-02-23T07:35:25.940732603Z at MongoClient.connect (/usr/src/app/node_modules/mongodb/lib/mongo_client.js:256:10)
2024-02-23T07:35:25.940736648Z at Function.MongoClient.connect (/usr/src/app/node_modules/mongodb/lib/mongo_client.js:401:22)
2024-02-23T07:35:25.940740476Z at connectToDatabase (/usr/src/app/node_modules/winston-mongodb/lib/winston-mongodb.js:138:32)
2024-02-23T07:35:25.940744236Z at new exports.MongoDB (/usr/src/app/node_modules/winston-mongodb/lib/winston-mongodb.js:153:5)
2024-02-23T07:35:25.940747973Z at new LoggerAdapter (/usr/src/app/node_modules/@noodl/cloudservice/dist/mongodb.js:60:22)
2024-02-23T07:35:25.940751746Z at createNoodlParseServer (/usr/src/app/node_modules/@noodl/cloudservice/dist/parse.js:35:20)
2024-02-23T07:35:25.940932942Z winston-mongodb: error initialising logger MongoParseError: Invalid connection string
2024-02-23T07:35:25.940943317Z at parseConnectionString (/usr/src/app/node_modules/mongodb/lib/core/uri_parser.js:575:21)
2024-02-23T07:35:25.940947520Z at connect (/usr/src/app/node_modules/mongodb/lib/operations/connect.js:282:3)
2024-02-23T07:35:25.940951379Z at /usr/src/app/node_modules/mongodb/lib/mongo_client.js:260:5
2024-02-23T07:35:25.940955032Z at maybePromise (/usr/src/app/node_modules/mongodb/lib/utils.js:692:3)
2024-02-23T07:35:25.940958672Z at MongoClient.connect (/usr/src/app/node_modules/mongodb/lib/mongo_client.js:256:10)
2024-02-23T07:35:25.940962666Z at Function.MongoClient.connect (/usr/src/app/node_modules/mongodb/lib/mongo_client.js:401:22)
2024-02-23T07:35:25.940966426Z at connectToDatabase (/usr/src/app/node_modules/winston-mongodb/lib/winston-mongodb.js:138:32)
2024-02-23T07:35:25.940970152Z at new exports.MongoDB (/usr/src/app/node_modules/winston-mongodb/lib/winston-mongodb.js:153:5)
2024-02-23T07:35:25.940975566Z at new LoggerAdapter (/usr/src/app/node_modules/@noodl/cloudservice/dist/mongodb.js:69:23)
2024-02-23T07:35:25.940981530Z at createNoodlParseServer (/usr/src/app/node_modules/@noodl/cloudservice/dist/parse.js:35:20)
2024-02-23T07:35:25.942472458Z MongoParseError: Invalid connection string
2024-02-23T07:35:25.942491171Z at parseConnectionString (/usr/src/app/node_modules/mongodb/lib/core/uri_parser.js:575:21)
2024-02-23T07:35:25.942495938Z at connect (/usr/src/app/node_modules/mongodb/lib/operations/connect.js:282:3)
2024-02-23T07:35:25.942499663Z at /usr/src/app/node_modules/mongodb/lib/mongo_client.js:260:5
2024-02-23T07:35:25.942504680Z at maybePromise (/usr/src/app/node_modules/mongodb/lib/utils.js:692:3)
2024-02-23T07:35:25.942668817Z at MongoClient.connect (/usr/src/app/node_modules/mongodb/lib/mongo_client.js:256:10)
2024-02-23T07:35:25.942677797Z at Function.MongoClient.connect (/usr/src/app/node_modules/mongodb/lib/mongo_client.js:401:22)
2024-02-23T07:35:25.942681677Z at MongoStorageAdapter.connect (/usr/src/app/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:170:42)
2024-02-23T07:35:25.942686762Z at MongoStorageAdapter._schemaCollection (/usr/src/app/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:225:17)
2024-02-23T07:35:25.942692812Z at MongoStorageAdapter.getAllClasses (/usr/src/app/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:412:17)
2024-02-23T07:35:25.942700823Z at MongoStorageAdapter.updateSchemaWithIndexes (/usr/src/app/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:939:17)
2024-02-23T07:35:34.593309338Z (node:1) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./public/" in the "exports" field module resolution of the package at /usr/src/app/node_modules/extract-files/package.json.
2024-02-23T07:35:34.593356404Z Update this package.json to use a subpath pattern like "./public/".
2024-02-23T07:35:34.593362118Z (Use node --trace-deprecation ... to show where the warning was created)
2024-02-23T07:35:34.594254801Z Noodl Parse Server listening at http://localhost:3000
2024-02-23T07:35:34.597150339Z winston-mongodb: error initialising logger MongoParseError: Invalid connection string

And this repeats forever!!!

Method 3:
Deploy via Github

The same errors as with method 2

If I create a directory on my server with the files from the repository and start docker compose up, both containers (MongoDB and the cloud service) are installed correctly and can also be used. However, I would very much like to run them via Caprover like the other apps - if only because of the https.

Can someone perhaps make sense of the error messages and tell me what I'm doing wrong? Probably the CLI method would be the easiest, because it is certainly closest to the docker compose, but I don't understand the error message that it is not a git root directory. What do I need to do differently to make it so?

I hope someone can help me because it would be very important to get this cloud service installed.

Thank you very much for your support!

[githubsaturn]

@SaschaValentin - this is an application error which is unrelated to CapRover

2024-02-23T07:35:25.942472458Z MongoParseError: Invalid connection string

Even if you run docker build and docker run you will see the exact same error. You need to find out what are the dependencies of your code. CapRover (and no other systems) can figure this out automatically for you.

[SaschaValentin]

Yes, I know this. It was only to point out, that all dependencies work correctly when you deploy it with docker-compose.

[githubsaturn]

You need to deploy all other containers that are defined in docker compose. For example, I see there is a mongodb image. You need to manually deploy that on CapRover.

[SaschaValentin]

Ah, okay, I didn't know, that I have to deploy all containers for themselves. Thought this would be done over the definition. Thanks for your help.

[githubsaturn]

If you look at your captain-definition you'll see that it only refers to the Dockerfile. In your Dockerfile, there is no mention of MongoDB

[SaschaValentin]

You really helped me a lot. All the different ways how you can deploy something to Caprover is a bit confusing for someone who is new to all this matter. I´ll try to get this running and maybe then I can write down a step-by-step instruction for all those who have the same problem.