Feature/readying for deployment (!226) · Merge requests · ifs / geometalab / osmaxx · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Nicola Jordan requested to merge feature/readying-for-deployment into develop Oct 04, 2015

Created by: ghost

Many many changes, sorry about that...

correct wrong settings for celery
better default settings in compose-common
include more settings, which should be configurable
added ssl settings as comments
added and removed again: deploy script

Tests:

Ran tests with RUN_E2E=true ./test.sh: all green.
Ran ./setup.production.sh:
- if ran more than once, it keeps the database: true
allowing login without csrf errors: true
login with clavid succeeds: true
extraction order can be placed as admin and non-admin: true

Reviewed by:

@das-g