impress

History

Matchu 024041e591 Configure nginx to send pre-gzipped files to the client Rails already creates little pre-gzipped `.gz` copies of all our assets in the `public/assets` directory when we build. This configures nginx to send those when available! We weren't doing any gzip stuff before, so this helps a lot with those bigger JS files, like the `wardrobe-2020` stuff. It's now at ~.5MB with compression, which is still a bit big, but nowhere near as offensive as the 4.5MB pre-anything, or 1.5MB post-minification, lol.		2023-10-25 15:44:01 -07:00
..
files	Configure nginx to send pre-gzipped files to the client	2023-10-25 15:44:01 -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.