impress

History

Emi Matchu 2e7bdc47d7 Move some Ansible config out of scripts and into `ansible.cfg` My immediate motivation is that I'm going to try turning on the pipelining setting, to improve performance, and I'd like to have the consistent place to put it! But also, I like standardizing our setup a bit more, too		2024-09-06 12:16:26 -07:00
..
files	Upgrade to Ruby 3.3.4 in production	2024-08-31 12:49:50 -07:00
ansible.cfg	Move some Ansible config out of scripts and into `ansible.cfg`	2024-09-06 12:16:26 -07:00
deploy.yml	Upgrade to Ruby 3.3.4 in production	2024-08-31 12:49:50 -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	Upgrade to Ruby 3.3.4 in production	2024-08-31 12:49:50 -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.