Stand up database server

[noamross]

• [x] CI workflow for pushing repel-infrastructure, updated containers running on Kirby
• [x] Database can be pushed from local workflow to server
• [x] Read-only access account for server (#6)
• [x] Static HTML page serving (for QA, status, repel-docs, etc.)
  • [x] Authentication (see eha-servers nginx/auth0 setup)
• [x] Logs / alerts (#8)
• [ ] put Rstudio password access back, since we'll be running an aegypti/prospero

Clean-up tasks:

• [x] scripts for .gitlab-ci.yml
• [x] remove BACKUP_FLAG from base docker-compose.yml and use docker-compose-dev.yml
• [x] function to export environment variables in scraper push/pull scripts
• [x] remote postgres and AWS commands for scraper push/pull scripts
• [x] clean-up error messages from push/pull scripts

[RobJY]

Here are my proposed SQL commands to create a read-only user:

revoke create on schema public from public;
create role repel_reader with login encrypted password 'yellow555zephyr222camera' nosuperuser 
inherit nocreatedb nocreaterole noreplication valid until 'infinity';
grant connect on database repel to repel_reader;
grant usage on schema public to repel_reader;
grant select on all tables in schema public to repel_reader;

As I mentioned in our meeting, this turns off crate table authority for everyone but root, so we'll have to run commands to turn it back on per user with:

grant create on schema public to givenuser;