comment correction (#4812)
This commit is contained in:
		
							parent
							
								
									7fc797da23
								
							
						
					
					
						commit
						57e50aa023
					
				
					 1 changed files with 2 additions and 2 deletions
				
			
		|  | @ -26,7 +26,7 @@ LOCAL_HTTPS=true | |||
| # ALTERNATE_DOMAINS=example1.com,example2.com | ||||
| 
 | ||||
| # Application secrets | ||||
| # Generate each with the `rake secret` task (`docker-compose run --rm web rake secret` if you use docker compose) | ||||
| # Generate each with the `RAILS_ENV=production bundle exec rake secret` task (`docker-compose run --rm web rake secret` if you use docker compose) | ||||
| PAPERCLIP_SECRET= | ||||
| SECRET_KEY_BASE= | ||||
| OTP_SECRET= | ||||
|  | @ -36,7 +36,7 @@ OTP_SECRET= | |||
| # You should only generate this once per instance. If you later decide to change it, all push subscription will | ||||
| # be invalidated, requiring the users to access the website again to resubscribe. | ||||
| # | ||||
| # Generate with `rake mastodon:webpush:generate_vapid_key` task (`docker-compose run --rm web rake mastodon:webpush:generate_vapid_key` if you use docker compose) | ||||
| # 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) | ||||
| # | ||||
| # For more information visit https://rossta.net/blog/using-the-web-push-api-with-vapid.html | ||||
| VAPID_PRIVATE_KEY= | ||||
|  |  | |||
		Loading…
	
		Reference in a new issue