safe-deploy.txt
I deploy <stack> to <host> by <how you deploy now: FTP, git pull, a
button>. During a deploy, visitors sometimes see errors.

Design a safer deploy for this host:
- Upload to a separate folder first, then switch over in one step, so no
  one ever sees half the new files and half the old.
- Database changes that are safe to run while the old code is still live.
- A cache-busting approach so browsers don't mix old CSS with new HTML.
- A rollback that takes one command or one click.

Keep it to what this host can actually do. I don't want tooling I can't
run here.

Uploading files one by one over live code is the usual cause of "it errored for a minute during the deploy". Switching a folder or a symlink makes the change instant.