- Started the brisket. Went on at 845am. I’m getting the process down pretty smoothly now.
- Listened to big bootie mix 15 for the first time.
- Submitted my purchase offer election and emailed the subsequent transmittal form. Requested 900.
- Ahhhh, this is what our dodgeball team is named after: https://www.youtube.com/watch?v=cVsQLlk-T0s.
- Went to del amo to pick up the bar end that they forgot to replace originally. Took it home and installed it myself, just a #5 billet assembly for the bar end that extends about a half inch for the #3 mirror assembly to clamp onto.
- You cannot use letsencrypt for local development. You cannot certify that you own an IP address, and you cannot certify that you own the generic “localhost” domain. Usually you can just provide yourself a self-signed certificate to make sure https works before you deploy to production.
- Many benchmarks of the original py3 release were slower than py2. That’s no longer the case, they’re close for most (or advantage 3).
- Worked an Autotest issue with briley, pointing toward the hyperion.shared.install_autotest module to show how to provision python workers with monorepo packages (to avoid conflicts with first-parties being used as third-parties).
- Supercontest
- Commented out the `COPY dump.sql -> docker-initd` in the database Dockerfile. If expects a db in the mounted volume, it shouldn’t rebuild an old one everytime. If you want to restore another database, do it manually.
- Shifted the development vs production workflows. Dev will just use runserver and flask with a simple sqlite database, no containers, no nginx, no postgres, no https.
- Set up automatic certification. Adds a 4th container, certbot, which exposes its certificates to the nginx container over a shared docker volume. It then runs certbot renew and nginx reload every few hours to ensure that they never expire.
- Because the current (whole) source directory is mounted, you CAN just make a change to the app on the host (on the droplet) and it will be reflected immediately in the app container (because the supercontest package is installed editably).
- Deployed to production
- Followed the instructions (I wrote) in ADMIN.md. Installed docker, created the secrets files, ran the cert initializer, then started the services.
- Copied the db backup over (from my laptop): scp -i ~/.ssh/digitalocean code/supercontest/backups/postgres/dump.sql southbaysupercontest.com:~
- Restored the data (on droplet): cat ~/dump.sql | docker exec -i postgres psql -U postgres
- Got https green, commited and pushed, closed ticket #27.
- Fully done with all 4 docker containers, a wonderful composition.