Skip to content

Production Runbook

Stuart Olivera edited this page Dec 14, 2017 · 7 revisions

Some notes on maintaining the website in production.

Asset cleanup

Rails and Dokku don't clean up old assets (css, js, images, etc) by itself. This means that on every deploy that an asset changes, both the new and old asset are kept on disk. Over time this can build up to a lot of excess, old assets.

Every once in a while, it's good to purge all assets and regenerate only the current ones.

Warning: this is a destructive, uptime-affecting action. Assets will throw a 404 error until the recompilation step is completed.

  1. SSH into the Dokku VM, and dokku enter brickhack-stage web
  2. From the shell, run rails assets:clobber. This will essentially rm -rf public/assets/
  3. Immediately after, run rails assets:precompile. This will regenerate the current assets.
  4. Exit the shell by entering exit. Dokku might not kill the temporary shell container otherwise.
Clone this wiki locally