impress

History

Matchu af705f1be0 Tighten the RAM limit bounds on the production impress service Lol ok, as I had kinda predicted, the memory bounds I set last time were not tight enough, and it stalled out again! (It was at 75% and fully just not working.) Let's try this tighter bound instead!		2023-10-27 10:32:33 -07:00
..
files	Tighten the RAM limit bounds on the production impress service	2023-10-27 10:32:33 -07: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	Extract some files out of the deploy script	2023-10-25 15:41:16 -07: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.