weixin_42455798 2011-08-10 15:16
浏览 209
已采纳

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

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

  • 写回答

2条回答 默认 最新

  • cutdeer 2011-08-19 16:30
    关注

    帮你转的

    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

    1. Install gems.

    bundle install

    1. 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

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

    mate config/mongoid.yml

    1. Run the application server.

    bundle exec unicorn_rails

    1. Open your browser.

    open http://localhost:8080/admin

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

    2. (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.

    1. First, create a Rails project.

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

    1. 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'

    1. Install gems

    bundle install

    1. Add the Locomotive config files and assets

    bundle exec rails g locomotive:install

    1. 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

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

    mate config/mongoid.yml

    1. Run the application server

    bundle exec unicorn_rails

    1. Open your browser

    open http://localhost:8080/admin

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

    2. (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

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)

报告相同问题?

悬赏问题

  • ¥15 一道python难题
  • ¥15 用matlab 设计一个不动点迭代法求解非线性方程组的代码
  • ¥15 牛顿斯科特系数表表示
  • ¥15 arduino 步进电机
  • ¥20 程序进入HardFault_Handler
  • ¥15 oracle集群安装出bug
  • ¥15 关于#python#的问题:自动化测试
  • ¥20 问题请教!vue项目关于Nginx配置nonce安全策略的问题
  • ¥15 教务系统账号被盗号如何追溯设备
  • ¥20 delta降尺度方法,未来数据怎么降尺度