-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a bunch of tools to backup/restore/init-db + dedicated docker service #153
Conversation
"prestart": "npm run build-prod", | ||
"serve-dev": "docker-compose -f compose-dev.yml up --force-recreate", | ||
"serve-dev": "docker-compose -p 6element -f compose-dev.yml up --force-recreate", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forcing the project name for more reliable container names.
npm run serve-dev # or npm run serve-prod in production environment | ||
|
||
# then in another window | ||
docker exec 6element_backup_1 tools/init-database.js | ||
docker-compose -f docker-compose-load-db.yml up | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why can't we do the same way as initdb docker exec 6element_backup_1 tools/load-database.js
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step should eventually disappear since it's about transfering a JSON file to the database. Eventually, the data will just be in the database with ways to make incremental changes.
Merge after @vallettea review and tests |
Add a bunch of tools to backup/restore/init-db + dedicated docker service
But please review.
This implements #107 (comment)
See Readme first.
This is only the dev part of the tooling. Adding the prod counter-part right now.