Suggested setup

1. adduser archiveooo. You can also have periodic_archiveooo and runner_archiveooo users with limited file access.

2. Checkout the code in /home/archiveooo/archiveooo

3. Create the /home/archiveooo/archiveooo/env virtualenv with requirements.txt

4. Create your /home/archiveooo/archiveooo/archiveooo/local_settings_outside_git.py -- see the example

5. Create the Postgres database and user or use the default local SQLite. Default Ubuntu settings should be fine.

6. Setup AWS EC2. You can have separate accounts for the main site and the periodic cleaner. See sample IAM policy.

7. Setup the non-cloudfronted website. See the Apache sample files in this folder. Make sure to expose the static files too: for instance, ln -sr ctfoood/static/ /var/www/html/ (+ Django's contrib/admin/static/admin/)

8. Create an S3 bucket to host public files. Otherwise, create dockerimg and public_files folders and link them in /var/www/html/.

9. Setup the periodic cleanup scripts: periodic_archiveooo.crontab and weekly_docker_cleanup.

10. Optionally, create accounts for Dockerhub and reCAPTCHA.

11. Optionally, setup email sending. In production, we use Postfix setup to talk to Amazon SES.

12. Optionally, setup AWS CloudFront. Our setup uses Origin cache headers (see the setup in views.py and in apache files), forwards all cookies and query strings.

13. Classic Django site setup:

./manage.py makemigrations
./manage.py makemigrations ctfoood
./manage.py migrate
./manage.py createsuperuser

14. Use the admin interface to create a group and add the superuser to it. (Chals are associated to the creator user's group, there's expected to be one.)