codeninjasllc/discourse
1
0
Fork 0
mirror of https://github.com/codeninjasllc/discourse.git synced 2024-11-30 10:58:31 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add clarification of how to set force_hostname

Browse source 
The original instructions told the user to log into Discourse Admin settings in order to set the force_hostname parameter so that the email validation URLs would be correct.  However, it is not possible to log in until email is validated.   This commit adds instructions for setting force_hostname through the console.
This commit is contained in:
Darren Nix 2013-04-23 10:47:32 -07:00
parent 2e8e4b7c6e
commit 6b54f1a6b0
1 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/HEROKU.md
View file

@ -128,7 +128,16 @@ For details on how to reduce the monthly cost of your application, see [Advanced
u.save u.save
``` ```
4. Provision the Heroku Scheduler. 4. In Discourse admin settings, set `force_hostname` to your applications Heroku domain.
This step is required for Discourse to properly form links sent with account confirmation emails and password resets. The auto detected application url would point to an Amazon AWS instance.
Since you can't log in yet, you can set `force_hostname` in the console.
```ruby
SiteSetting.create(:name => 'force_hostname', :data_type =>1, :value=>'yourappnamehere.herokuapp.com')
```
5. Provision the Heroku Scheduler.
This will allow Heroku Scheduler to cue up tasks rather than running a separate clock process. This will allow Heroku Scheduler to cue up tasks rather than running a separate clock process.
In the [Heroku dashboard](https://dashboard.heroku.com/apps), select your app, then click on **Heroku Scheduler Standard** under your Add-ons. In the [Heroku dashboard](https://dashboard.heroku.com/apps), select your app, then click on **Heroku Scheduler Standard** under your Add-ons.
@ -146,7 +155,7 @@ For details on how to reduce the monthly cost of your application, see [Advanced
rake version_check Daily 01:00 rake version_check Daily 01:00
5. Start Sidekiq. 6. Start Sidekiq.
In the [Heroku dashboard](https://dashboard.heroku.com/apps), select your app and you will see the separate processes that have been created for your application under Resources. You will only need to start the sidekiq process for your application to run properly. The clock process is covered by Heroku Scheduler, and you can even remove this from the Procfile before deploying if you so wish. The worker process has been generated as a Rails default and can be ignored. As you can see **the Sidekiq process costs $34 monthly** to run. If you want to reduce this cost, check out [Advanced Heroku deployment](#advanced-heroku-deployment). In the [Heroku dashboard](https://dashboard.heroku.com/apps), select your app and you will see the separate processes that have been created for your application under Resources. You will only need to start the sidekiq process for your application to run properly. The clock process is covered by Heroku Scheduler, and you can even remove this from the Procfile before deploying if you so wish. The worker process has been generated as a Rails default and can be ignored. As you can see **the Sidekiq process costs $34 monthly** to run. If you want to reduce this cost, check out [Advanced Heroku deployment](#advanced-heroku-deployment).
@ -212,10 +221,6 @@ Using Foreman to start the application allows you to mimic the way the applicati
+ :authentication => :plain + :authentication => :plain
+ } + }
``` ```
3. In Discourse admin settings, set `force_hostname` to your applications Heroku domain.
This step is required for Discourse to properly form links sent with account confirmation emails and password resets. The auto detected application url would point to an Amazon AWS instance.
## Advanced Heroku deployment ## Advanced Heroku deployment