Name: elcid-deployment
Owner: Open Health Care
Description: Deployment and setup scripts for elCID
Created: 2016-08-03 14:11:44.0
Updated: 2016-08-03 14:12:00.0
Pushed: 2018-01-10 13:40:34.0
Homepage: null
Size: 59
Language: Python
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
clone git@github.com:openhealthcare/elcid-deployment.git
lcid-deployment
rtualenv elcid-setup -a $PWD
install -r requirements.txt
ettings.ini.example settings.in
You should be up and running!
Deployment to Test does not set up the cron job syncing.
Set env.db_dump_dir to load in a database dump
Deployment to production sets up a dump directory. It assumes this is the same directory on a different server. It will load in the most recent database dump.
You want to do regular database back ups. These will get put in env.db_dump_dir. On a remote host at env.sync_host. These are set up by default if you do fab deploy_prod, or you can do it yourself with
setup_cron
All Postgres and Pip methods from postgres_helper are exposed, run the task postgres, with you method name, followed by args, kwargs.
for example
postgres:get_recent_database_dump_path
will return the latest database dump with full path.
If you want to refresh the current database. Ie drop it and load in the latest database dump you can use
postgres:refresh_database