想学习一下rails开源cms locomotive 无奈官网要翻wall,有没有同学安装过呀 求ubuntu下安装指导
Requirements
Ruby
Of course :-)
We tested it with both Ruby 1.8.7 (2009-06-12 patchlevel 174) and Ruby 1.9.2.p0 which are two of Ruby versions Heroku supports.
Please note that performances are much better with Ruby 1.9.2 and the stability seems okay (no bugs found for now).
Mongodb
Locomotive CMS does not use a classic sql database such as mysql or postgresql but rather a nosql database named mongodb.
Mongodb is available on many OS. Check this link out for more information.
Note: We suggest you to take a version from 1.6.0.
ImageMagick
Uploaded images for asset collections are cropped, for example, and Locomotive uses ImageMagick for this purpose. Again, ImageMagick is available on a large set of OS.
Browsers (back-office)
We haven't had time to test the IE versions. So for now, we ask you to use the Locomotive back-office with the following browsers: Safari, Firefox and Chrome.
From source installation
This way of installing Locomotive is recommended when you want to add new features, correct bugs or see how Locomotive works internally.
git clone git://github.com/locomotivecms/engine.git locomotive
cd locomotive
bundle install
mate config/initializers/locomotive.rb
Note: If you run Locomotive in local and with the multi-sites mode on, do not forget to update your /etc/hosts file accordingly.
By default, Locomotive uses Amazon S3 in production. To change it, modify the carrierwave initialization file.
mate config/initializers/carrierwave.rb
mate config/mongoid.yml
bundle exec unicorn_rails
open http://localhost:8080/admin
Follow the instructions in the browser to create your first account and site.
(ONLY IN PRODUCTION) Push the assets used by the Locomotive back-office to Amazon S3 for better performances.(Jammit-S3).
export S3_KEY_ID=
export S3_SECRET_KEY=
export S3_BUCKET=
jammit-s3 --force
If you do not want to push the assets in S3 and instead leave them in your application, remove the lines about S3 in the config/assets.yml file and run the following command:
jammit --force
Engine installation
This is probably the cleanest way to build your own comprehensive hosting CMS platform because the Locomotive core cannot be broken and all you need to do is add your own content.
rails new my_platform -O -T -J
cd my_platform
rm public/index.html
gem 'rails', '3.0.9'
gem 'locomotive_cms', :git => 'git://github.com/locomotivecms/engine.git', :require => 'locomotive/engine'
gem 'unicorn', :group => 'development'
bundle install
bundle exec rails g locomotive:install
mate config/initializers/locomotive.rb
By default, Locomotive uses Amazon S3 in production. To change it, modify the carrierwave initialization file.
mate config/initializers/carrierwave.rb
mate config/mongoid.yml
bundle exec unicorn_rails
open http://localhost:8080/admin
Follow the instructions in the browser to create your first account and site.
(ONLY IN PRODUCTION) Push the assets used by the Locomotive back-office to Amazon S3 for better performances (Jammit-S3).
export S3_KEY_ID=
export S3_SECRET_KEY=
export S3_BUCKET=
jammit-s3 --force
If you do not want to push the assets in S3 but leave them in your application instead, remove the lines about S3 in the config/assets.yml file and run the following command
jammit --force
你去github上找找就可以了吧,何必翻*墙?