想学习一下rails开源cms locomotive 无奈官网要翻wall，有没有同学安装过呀求ubuntu下安装指导

问答首页 → 编程语言技术

0 0

想学习一下rails开源cms locomotive 无奈官网要翻wall，有没有同学安装过呀求ubuntu下安装指导5

Rails

2011年8月10日 15:16

siy124
5
0 0 0

2个答案按时间排序按投票排序

0 0

采纳的答案

帮你转的
--------------------------------------------
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.

1. Get source code from github.

git clone git://github.com/locomotivecms/engine.git locomotive
cd locomotive

2. Install gems.

bundle install

3. Edit the Locomotive settings.

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

4. You also may want to change your mongodb connection settings.

mate config/mongoid.yml

5. Run the application server.

bundle exec unicorn_rails

6. Open your browser.

open http://localhost:8080/admin

7. Follow the instructions in the browser to create your first account and site.

8. (ONLY IN PRODUCTION) Push the assets used by the Locomotive back-office to Amazon S3 for better performances.(Jammit-S3).

export S3_KEY_ID=<your s3 key id>
export S3_SECRET_KEY=<your s3 secret key>
export S3_BUCKET=<your s3 bucket name>

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.

1. First, create a Rails project.

rails new my_platform -O -T -J
cd my_platform
rm public/index.html

2. You have to tell your Rails app that you want to include the Locomotive gem available on Gemcutter. Edit your application Gemfile and add these lines if missing.

gem 'rails', '3.0.9'
gem 'locomotive_cms', :git => 'git://github.com/locomotivecms/engine.git', :require => 'locomotive/engine'
gem 'unicorn', :group => 'development'

3. Install gems

bundle install

4. Add the Locomotive config files and assets

bundle exec rails g locomotive:install

5. Edit the locomotive settings

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

6. You also may want to change your mongodb connection settings

mate config/mongoid.yml

7. Run the application server

bundle exec unicorn_rails

8. Open your browser

open http://localhost:8080/admin

9. Follow the instructions in the browser to create your first account and site.

10. (ONLY IN PRODUCTION) Push the assets used by the Locomotive back-office to Amazon S3 for better performances (Jammit-S3).

export S3_KEY_ID=<your s3 key id>
export S3_SECRET_KEY=<your s3 secret key>
export S3_BUCKET=<your s3 bucket name>

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