impress-2020

OpenNeo/impress-2020

History

Matchu 0c2939dfe4 Use Puppeteer instead of Playwright We used Playwright in the first place to try to work around a Vercel deploy issue, and I'm not sure it really ended up mattering lol :p But yeah, I'm putting the new Puppeteer code through the same prod stress test, and it just doesn't seem to be getting into the same broken state that Playwright was. I'm guessing it's just that Puppeteer has more investment in edge-case handling? (There's also the fact that we're no longer running things as root, which could have been a fucky problem, too?)		2021-11-13 02:16:58 -08:00
..
playbooks	Use Puppeteer instead of Playwright	2021-11-13 02:16:58 -08:00
authorized-ssh-keys.txt	Add SSH keys to deploy-setup	2021-11-12 20:14:44 -08:00
inventory.cfg	Ansible tasks to set up web user, install Node	2021-11-02 16:01:30 -07:00
README	Add more details to deploy README	2021-11-02 21:14:54 -07:00

README

Impress 2020 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!