impress

History

Emi Matchu b18dd115a1 Build Ruby 3.3.0, but don't switch over to it yet Still need to test the app with it, and getting this to deploy right will be a bit tricky! Here's my thinking for sequencing once the code is ready: 1. Temporarily modify `deploy.yml` to push the version, but not set it as `current` or restart the app. 2. Update the service file to use Ruby 3.3.0 and reference that version directly (instead of `current`), and restart the app. 3. Once it's already running, link that version as `current`. 4. Update the service file to reference `current` as usual, and restart the app.		2024-02-22 11:48:48 -08:00
..
files	Add redirect from openneo.net to impress.openneo.net	2024-02-20 10:35:59 -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	Build Ruby 3.3.0, but don't switch over to it yet	2024-02-22 11:48:48 -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.