Make scalingo doc clearer
This commit is contained in:
		
							parent
							
								
									2ecc791d9a
								
							
						
					
					
						commit
						f210b2b7ef
					
				
					 1 changed files with 2 additions and 2 deletions
				
			
		|  | @ -8,6 +8,6 @@ Scalingo guide | |||
|   * You can use a .scalingo.io domain, which will be simple to set up, or you can use a custom domain. | ||||
|   * You will want Amazon S3 for file storage. The only exception is for development purposes, where you may not care if files are not saved. Follow a guide online for creating a free Amazon S3 bucket and Access Key, then enter the details. | ||||
|   * If you want your Mastodon to be able to send emails, configure SMTP settings here (or later). Consider using [Mailgun](https://mailgun.com) or similar, who offer free plans that should suit your interests. | ||||
| 3. Deploy! The app should be set up, with a working web interface and database. You can change settings and manage versions from the Heroku dashboard. | ||||
| 3. Deploy! The app should be set up, with a working web interface and database. You can change settings and manage versions from the Scalingo dashboard. | ||||
| 
 | ||||
| You may need to use the `scalingo` CLI application to run `USERNAME=yourUsername rails mastodon:make_admin` to make yourself an admin. | ||||
| To make yourself an admin, you can use the `scalingo` CLI: `scalingo run -e USERNAME=yourusername rails mastodon:make_admin`. | ||||
|  |  | |||
		Loading…
	
		Reference in a new issue