Installation

git clone [email protected]:openhealthcare/elcid-deployment.git
cd elcid-deployment
mkvirtualenv elcid-setup -a $PWD
pip install -r requirements.txt
cp settings.ini.example settings.in

Server Setup

1. run ./initial_bootstrap.sh
2. workon elcid-setup
3. Edit the variables in `settings.ini as required.
4. install the requirements file
5. fab server_setup

You should be up and running!

Deployment Test

Deployment to Test does not set up the cron job syncing.

Set env.db_dump_dir to load in a database dump

1. workon elcid-setup
2. Edit the variables in `settings.ini as required.
3. fab deploy_test
4. fab restart_everything

Deployement to Production

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.

1. workon elcid-setup
2. Edit the variables in `settings.ini as required.
3. fab deploy_prod
4. fab restart_everything

Database Back ups.

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

fab setup_cron

Utility

All Postgres and Pip methods from postgres_helper are exposed, run the task postgres, with you method name, followed by args, kwargs.

for example

fab 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

fab postgres:refresh_database