Tools to deploy a dev site via docker/ECS, including post-launch commands

[cgolubi1]

• Partially addresses #2908

What this includes:

• It does an end-to-end creation of a site for a dev branch on ECS, assuming you have docker available on your local computer and have access to the AWS account which owns DNS for buttonweavers.com, with no specialized configuration or manual actions needed
• Functionality includes:
  • Create a docker image using the Dockerfile (which was patterned off our CircleCI docker config for simplicity --- agree that we should move to a newer OS, but that's not the part of the ocean we are boiling at this time)
  • Create an ECR repo for this branch if necessary, and upload the docker image we created to that repo, tagged with the branch/commit ID
  • Create an ECS service for this branch if necessary, create a new revision of a task definition using the image version we uploaded, and create/update a single task in the service to run that task definition
  • Once the container is running and has a public IP, update DNS so that the FQDN ${BRANCH_WITH_HYPHENS}.${USERNAME}.dev.buttonweavers.com points to that container
  • Run post-install actions on the container via SSH: setup LetsEncrypt so the SSL site will work, load a database backup from the local computer if one was provided, set the site type to "development"
• Functionality we don't have yet:
  • Run database modification scripts from the PR after loading the database
  • Script teardown of the per-branch ECS service, ECR repo, and DNS name, so i don't have to pay for them
  • Support an RDS database rather than a local one (blocker for staging/prod)
  • Support an ECS service with a static IP attached to a load balancer (blocker for staging/prod)
  • Attach a remote filesystem at /srv/backup to which database backups are being run (blocker for staging/prod)
  • Stand up a replay-testing site (blocker for pushing logic changes that we want to regression-test using random games)
• The container has some convenience functionality (postfix, cron), and i was able to receive a verification e-mail for a new user, but it's pretty bare-bones, and i'm sure i'm going to discover stuff we're missing while this is under test

Testing:

• The command env AWS_PROFILE=bm_deploy /Users/chaos/games/buttonmen/miniconda3/bin/python ./deploy/docker/deploy_buttonmen_site was used to deploy the dev site at https://2908-docker-config.cgolubi1.dev.buttonweavers.com/ui/ using the most recent staging database i downloaded (from the last time i deployed prod in March) - please check out that dev site and see if you see anything weird about it

[cgolubi1]

Passing circleci run: https://app.circleci.com/pipelines/github/cgolubi1/buttonmen/198/workflows/d2529bd5-0678-4286-b1d2-26ac60503391

[cgolubi1]

My running list of things i forgot to do, for my own use (i'm not convinced any of these are blockers, because this is very far from the last PR that's going to be involved in this project):

• Define a per-site environment variable in /etc/crontab so i can see which site was responsible for a particular cron email without having to fish for it
• /etc/cron.daily/logrotate tries to run and fails, presumably because of missing dependencies in the barebones OS image

[blackshadowshade]

I was able to:

• log in
• see active/stale games on the Overview page
• click through to a stale game
• join an open game
• choose a swing value
• play a turn
• view the forums
• create a thread
• view the help
• view the skills page
• view the button set page
• view a button page
• view and change the settings page successfully, with new settings applied

That looks pretty good!

@cgolubi1, do you want me to accept this pull request in this current state and then progress this incrementally?

[cgolubi1]

Sure, go for it. That lets you merge it into the Pappy/Bruno PR, and then i can do an end-to-end test on that branch.

Thanks!

[blackshadowshade]

Merging now then!