I added a line to activate the user from the rails console, for the case when the mail server hasn't been configured yet and discourse can't send activation mails.
* ubuntu should be Ubuntu
* Ubuntu 12.04 should be Ubuntu Server 12.04 or Ubuntu Server 12.04 LTS (preferred by Ubuntu Community)
* Consistent capitalization of "Discourse"
* add screenshots from Ubuntu config process
* add instructions for updating predeployed VMs
* add details on configuring mail server
* don't install test gems into prod
* no need for bundle exec
* small cleanups
* added RVM option for single-user install
* clarified Web Server options
* bluepill sample config: create socket directory if it doesn't exist
* add multisite.yml.production-sample
* rename production.sample.rb (OCD)
* make two database.yml samples (one for dev, one for prod)
* fixed travis build (database.yml.sample renamed)
* fix other references to database.yml.sample
* clean up 'rvm requirements' instructions as per @mpapis
This helps if somebody would fork a GitHub repository, as the links
now lead to files in fork, not files in original repository. Also, it
makes more sense when reading Markdown files locally.
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.
Probably not 100% complete yet, but covers enough to pass all specs.
NOTE: requires either libXML2 2.7.6 or the separately submitted fix to
pretty_text_spec.rb
This was the proposed change to add an optional step for including and configuring the Autoscaler Gem in the HEROKU.md doc. I've included a pastable version of the Sidekiq initializer file that only adds the autoscaler middleware in production.
