Mention `yarn install` in production upgrade guide (#62)

This commit is contained in:
Sergiusz Bazański 2017-04-19 17:44:07 +01:00 committed by wxcafé
parent 40fcc558cc
commit 95a6040458
1 changed files with 7 additions and 1 deletions

View File

@ -288,9 +288,15 @@ If you want a stable release for production use, you should use tagged releases.
As part of your deploy, you may need to run:
- `RAILS_ENV=production bundle exec rails db:migrate`
if anything in the `/db/` directory has changed, and/or
- `yarn install`
- `RAILS_ENV=production bundle exec rails assets:precompile`
Depending on which files changed, e.g. if anything in the `/db/` or `/app/assets` directory changed, respectively. Also, Mastodon runs in memory, so you need to restart it before you see any changes. If you're using systemd, that would be:
if anything in the `/app/assets` directory changed.
Also, Mastodon runs in memory, so you need to restart it before you see any changes (including new precompiled assets). If you're using systemd, that would be:
```sh
sudo systemctl restart mastodon-*.service