Browse Source

Updated docker-compose snippet to a working one (#13196)

added 'bundle exec' before rake
Denis Teyssier 2 months ago
parent
commit
73f3842284
No account linked to committer's email address
1 changed files with 2 additions and 2 deletions
  1. 2
    2
      .env.production.sample

+ 2
- 2
.env.production.sample View File

@@ -33,7 +33,7 @@ LOCAL_DOMAIN=example.com
33 33
 # ALTERNATE_DOMAINS=example1.com,example2.com
34 34
 
35 35
 # Application secrets
36
-# Generate each with the `RAILS_ENV=production bundle exec rake secret` task (`docker-compose run --rm web rake secret` if you use docker compose)
36
+# Generate each with the `RAILS_ENV=production bundle exec rake secret` task (`docker-compose run --rm web bundle exec rake secret` if you use docker compose)
37 37
 SECRET_KEY_BASE=
38 38
 OTP_SECRET=
39 39
 
@@ -42,7 +42,7 @@ OTP_SECRET=
42 42
 # You should only generate this once per instance. If you later decide to change it, all push subscription will
43 43
 # be invalidated, requiring the users to access the website again to resubscribe.
44 44
 #
45
-# Generate with `RAILS_ENV=production bundle exec rake mastodon:webpush:generate_vapid_key` task (`docker-compose run --rm web rake mastodon:webpush:generate_vapid_key` if you use docker compose)
45
+# Generate with `RAILS_ENV=production bundle exec rake mastodon:webpush:generate_vapid_key` task (`docker-compose run --rm web bundle exec rake mastodon:webpush:generate_vapid_key` if you use docker compose)
46 46
 #
47 47
 # For more information visit https://rossta.net/blog/using-the-web-push-api-with-vapid.html
48 48
 VAPID_PRIVATE_KEY=

Loading…
Cancel
Save