These are chat archives for locomotivecms/v3

17th
Nov 2015
Didier Lafforgue
@did
Nov 17 2015 00:06
require ‘locomotive/steam/liquid/tags/concerns/i18n_page’
require ‘locomotive/steam/liquid/tags/concerns/path’
at the top of the file
Didier Lafforgue
@did
Nov 17 2015 01:08
@/all we now have support for MongoDB 2.0, 3.0 / Mongoid 5.0. Use the very last commit of Engine.
Let me know if you run into issues.
Antoine Mainguy
@amainguy
Nov 17 2015 14:37
thanks @did. just requiring 'locomotive/steam' works perfectly!
Didier Lafforgue
@did
Nov 17 2015 14:41
glad to hear this @amainguy!
S Tunji Turner
@stunjiturner
Nov 17 2015 18:12
@did gem 'locomotive_cms', git: 'git://github.com/locomotivecms/engine.git', :ref => 'e68a800fd1d3beee3abdd8094d870066a53662d6’ does not work, how to get the latest commit?
had the wrong URL, got it
S Tunji Turner
@stunjiturner
Nov 17 2015 18:30
error deploying on heroku
/app/vendor/bundle/ruby/2.2.0/gems/carrierwave-aws-1.0.0/lib/carrierwave/storage/aws_file.rb:15:in `file': undefined method `object' for nil:NilClass (NoMethodError)
Didier Lafforgue
@did
Nov 17 2015 19:00
hi @stunjiturner!
could you show me your config/initializers/carrierwave.rb file please?
S Tunji Turner
@stunjiturner
Nov 17 2015 20:16
@did I fixed by adding a heroku config var S3_BUCKET actual name in carrier wave file , instead of using S3_BUCKET_NAME locomotive docs
Didier Lafforgue
@did
Nov 17 2015 21:02
@stunjiturner I’ll check the documentation then, thanks!
S Tunji Turner
@stunjiturner
Nov 17 2015 22:36
@did the
@did I used heroku-instant-deploy , the configuration web ui asked for S3_BUCKET_NAME , so this needs to be fixed as well.