woop! upstream already had the change to `package.json`.

@broken@mastodon.social no problem... the chain of steps starts with "In `package.json`...". I guess I could have numbered them, too. :-/

@Gargron@mastodon.social your current Docker solution is actually pretty nice. I ended up on Heroku because I already had a dozen projects on there. now I have an even thirteen...

@Gargron@mastodon.social I'm definitely interested. I'll wrap these up in a PR and start a discussion.

@broken@mastodon.social I posted several follow-up messages with more detail (unfortunately, I didn't use the reply to chain them).

@Gargron@mastodon.social uhhh, right :-( need an edit button...

Configure SMTP or users won't be able to activate new accounts. Definitely configure S3 for file storage, or your uploads (uploaded to `tmp`) will disappear every time the Heroku dyno restarts!

Finish by configuring the Heroku environment (using `.env.production.sample` as a guide). Definitely configure `LOCAL_DOMAIN` and `LOCAL_HTTPS` correctly. (I didn't do this immediately and as a consequence the first handful of people I followed saw me as a user on an instance running on `localhost`.) For `PAPERCLIP_SECRET` and `SECRET_KEY_BASE` I ran `rake secret` in another Rails project to generate the secret keys.

Fix Paperclip by changing `s3_permissions` from "public" to "public-read" in `config/initializers/paperclip.rb`. I'm pretty sure this is a bug. I need to investigate a bit more and then submit a PR.

Create a `Procfile`:

web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq -c 5 -v -q default -q mailers -q push