Conversation
smalho01
approved these changes
Feb 7, 2023
Collaborator
|
wait to merge until rems-303 is merged |
Contributor
Author
|
this PR builds off 303, so it can either be merged into that PR or the base branch can change to dev after 303 is pulled in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
The server will now default to using mongo. If you launch using docker you will have to change the mongo hostname in the config to use the url of the deployed database. You can also test with a local database by starting mongo on your machine and changing the hostname to match the url of the database (likely localhost: 27017).
To launch the database with docker, use:
docker run --name rems_local_pims_remsadmin_mongo --expose 27017 -p 27017:27017 -e MONGO_INITDB_ROOT_USERNAME='username' -e MONGO_INITDB_ROOT_PASSWORD='password' -v rems_local_pims_remsadmin_mongo:/data/db -v "$(pwd)"/mongo-init.js:/docker-entrypoint-initdb.d/mongo-init.js mongoThen put your chosen username and password in the env file like so:
note that if you have already launched through docker, a user will already be created and you will either have to delete the database to create a new one with a new user, or just use the user that was originally made.
After setting up the database, you can use the app and it should update the database with the data on launch. You can use a tool like mongo Compass to see the data being populated.
Issue ticket number and Jira link
REMS-304
Checklist before requesting a review
devnot main (the only exception to this is releases fromdevand hotfix branches)Checklist for conducting a review
Workflow
Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.