impress

History

Emi Matchu e9b0fa0779 Future-proof our nginx config for IPv6 Today I learned that nginx requires a special invocation to listen to IPv6 addresses as well as IPv4. On some of my other projects, this was causing Let's Encrypt certificate renewal to fail, because Let's Encrypt prefers to connect over IPv6 when an AAAA record is present, so its challenges were always returning 404, because nginx wasn't listening on IPv6. This shouldn't be affecting impress in production, because we don't have an AAAA record right now. But I'm just making this change in all my projects, to make sure this doesn't bite me in the future!		2024-02-13 08:52:45 -08:00
..
files	Future-proof our nginx config for IPv6	2024-02-13 08:52:45 -08:00
deploy.yml	Clarify a note in the deploy playbook	2023-10-23 19:05:09 -07:00
inventory.cfg	Remove beta.impress.openneo.net from deploy setup	2023-10-25 15:22:50 -07:00
README	Create setup.yml deploy script	2023-10-23 19:05:09 -07:00
setup.yml	Add support_staff flag to user record; they can use Support tools	2024-01-29 04:21:19 -08:00

README

Dress to Impress is deployed to a VPS server. We use this Ansible Playbook to
automate the environment setup!

We expect to be deploying to Ubuntu 20.04 LTS, initially with nothing
installed. The user you deploy with should have sudoers access. That should be
all it takes!

First, run `yarn deploy:setup` in the app root, to run the `setup.yml`
playbook. This will prompt you for your root password, to set up system
dependencies. It should be safe to re-run this, including if you add a new
dependency to the playbook, because the steps are non-destructive and Ansible
will skip steps that are already satisfied.

Then, to deploy a new version of the app, run `yarn deploy`. This will build
the app from the code on your machine, then send the source and build output
to the remote machine, and switch it to be the new production version. Nice!

Note that the setup script references a file named `production.env`, which is
gitignored because it contains sensitive information, like database passwords.
You should create a `production.env` file in the local `deploy/files`
directory, to be copied to the remote server and used as its environment
variables.