forked from browsermedia/browsercms
-
Notifications
You must be signed in to change notification settings - Fork 9
Deploying to Heroku
peakpg edited this page May 14, 2012
·
14 revisions
These are my initial notes on making BrowserCMS work on Heroku, which is intended for release in v3.5.0
Create the project using sqlite (there are issues generating with -d postgresql
syntax).
- Disable Caching
This will avoid the issue where files are written out and stops the cms subdomain redirects.
# config/environments/production.rb
config.action_controller.perform_caching = false
- Configure Postgresql in production
# Gemfile
gem 'sqlite3', :group=>:development
gem 'pg', :group=>:production
# config/database.yml
production:
adapter: postgresql
encoding: unicode
database: heroku_app_production
pool: 5
username: heroku_app_user
password: heroku_app_pw
- https://devcenter.heroku.com/articles/rails3
- Mailing List Discussion: https://groups.google.com/forum/?fromgroups#!topic/browsercms/WCFUn82wJeg
- Sample Gemfile Gist: https://gist.github.com/1878874
- RefineryCMS's Heroku Guide: http://refinerycms.com/guides/heroku
- Heroku S3 Guide: https://devcenter.heroku.com/articles/s3
- Paperclip and S3: http://webtempest.com/how-to-allow-image-uploads-in-rails-on-heroku/