forked from OpenNeo/impress
Emi Matchu
abbde80f60
It's finally colocated onto this box, instead of being on the old server! I think I'm noticing substantial perf improvements, probably both from increased colocation (tho they were in the same house before), and also from like ten years of performance optimizations LOL! As part of this, I created a new `setup_secrets.yml` file that's similar to `production.env`, but is for values that the setup script itself needs access to, whereas `production.env` is for values that the app needs at runtime. (Though they have some things in common, like the MySQL user password!) It's gitignored for security, as per usual! |
||
|---|---|---|
| .. | ||
| files | ||
| deploy.yml | ||
| inventory.cfg | ||
| README | ||
| setup.yml | ||
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.