From 445dc18cd9541c068d17575e8559e64c88bf6595 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20S?= <benpro@benpro.fr>
Date: Wed, 14 Jun 2017 17:40:01 +0200
Subject: [PATCH] Missing RAILS_ENV=production and bundle exec
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

If you're omitting RAILS_ENV and `bundle exec` you'll have:

~~~
rake aborted!
NameError: uninitialized constant Annotate
[…]
~~~
---
 Running-Mastodon/Production-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Running-Mastodon/Production-guide.md b/Running-Mastodon/Production-guide.md
index eb57707..ba88e64 100644
--- a/Running-Mastodon/Production-guide.md
+++ b/Running-Mastodon/Production-guide.md
@@ -237,7 +237,7 @@ Then you have to configure your instance:
 
 Fill in the important data, like host/port of the redis database, host/port/username/password of the postgres database, your domain name, SMTP details (e.g. from Mailgun or equivalent transactional e-mail service, many have free tiers), whether you intend to use SSL, etc. If you need to generate secrets, you can use:
 
-    rake secret
+    RAILS_ENV=production bundle exec rake secret
 
 To get a random string. If you are setting up on one single server (most likely), then `REDIS_HOST` is localhost and `DB_HOST` is `/var/run/postgresql`, `DB_USER` is `mastodon` and `DB_NAME` is `mastodon_production` while `DB_PASS` is empty because this setup will use the ident authentication method (system user "mastodon" maps to postgres user "mastodon").