We are currently using Atlas because to use the mongo on img01 has cost too much development time and is bloating the scope of the initial POC deployment for feedback.
Set the mongo connection string for the img server on dev and prod and use npm run dbTests to test the connection to the mongo. At this time, we are getting the following error
Note that the .env files on the devs' localhost, the development server, and the production server will need to be updated with the new connection string once we have confirmed it is working.
Note that this repository's secrete env variables will need to be updated with the the new connection settings once we have confirmed it is working.
Note that the CI/CD pipeline will need to be checked once we change these settings to make sure GH Action tests can connect to the mongodb and complete successfully.
We are currently using Atlas because to use the mongo on img01 has cost too much development time and is bloating the scope of the initial POC deployment for feedback.
Set the mongo connection string for the img server on dev and prod and use
npm run dbTeststo test the connection to the mongo. At this time, we are getting the following errorNote that the
.envfiles on the devs' localhost, the development server, and the production server will need to be updated with the new connection string once we have confirmed it is working.Note that this repository's secrete env variables will need to be updated with the the new connection settings once we have confirmed it is working.
Note that the CI/CD pipeline will need to be checked once we change these settings to make sure GH Action tests can connect to the mongodb and complete successfully.