deployment workflow set up, documentation and testing

[Hagellach37]

postgres and wal-g configuration:

• [x] expose postgres port to host in docker-compose
• [x] add to WALG_GS_PREFIX to .env
• [x] add google service account key

clarify where mapswipe_workers config files are stored on server (not inside docker container):

• [x] /usr/share/config/mapswipe_workers/ ormapwipe_workers/config/` --> will be in mapwipe_workers/config/

test_config.py script to test if configuration is complete

• [x] Add test for Wal-G, and google cloud storage service account key
• [x] get server name from nginx config file

nginx and let's encrypt

• [x] double check that certificates get created after server restart

deploy script

• [x] write deploy.sh script
• [x] add mapswipe_workers tests to deploy.sh or run tests in another docker container?
• [ ] what happens if something fails in the middle? is it a disaster?
• [ ] don't deploy if building of a single container failed
• [ ] is there some old data you need to delete once the process is complete? (to prevent filling up your disk)

[Matthias-Schaub]

Note on the deployment script and tests:

Running mapswipe_workers tests should only be done in test environment such as dev server or inside CI environment (Tavis). Currently deploy.sh is also used in production evironment. We do not want to let tests scripts interact with production firebase and postgres.

I suggest running tests in CI and manually for production but do not run tests in deploy.sh

[Hagellach37]

need to close this and break up in smaller parts,