In order to be able to run this other than on production, let's keep a known good configuration in Gemfile.lock.
This way, I won't have to guess what or when this broke: Unable to activate actionpack-3.2.19, because rack-1.5.2 conflicts with rack (~> 1.4.5) (Gem::LoadError)
foreman start /opt/src/opensource/ruby/coderdojowebstorage
21:41:57 web.1 | started with pid 4955
21:41:58 web.1 | I, [2014-10-01T21:41:58.652688 #4955] INFO -- : listening on addr=0.0.0.0:8080 fd=9
21:41:58 web.1 | I, [2014-10-01T21:41:58.654399 #4955] INFO -- : master process ready
21:41:58 web.1 | I, [2014-10-01T21:41:58.655518 #4956] INFO -- : Refreshing Gem list
21:42:00 web.1 | /Users/olle/.rbenv/versions/2.0.0-p481/lib/ruby/2.0.0/rubygems/specification.rb:2007:in `raise_if_conflicts': Unable to activate actionpack-3.2.19, because rack-1.5.2 conflicts with rack (~> 1.4.5) (Gem::LoadError)
21:42:00 web.1 | from /Users/olle/.rbenv/versions/2.0.0-p481/lib/ruby/2.0.0/rubygems/specification.rb:1176:in `activate'
21:42:00 web.1 | from /Users/olle/.rbenv/versions/2.0.0-p481/lib/ruby/2.0.0/rubygems/specification.rb:1212:in `block in activate_dependencies'
21:42:00 web.1 | from /Users/olle/.rbenv/versions/2.0.0-p481/lib/ruby/2.0.0/rubygems/specification.rb:1198:in `each'
In order to be able to run this other than on production, let's keep a known good configuration in Gemfile.lock.
This way, I won't have to guess what or when this broke:
Unable to activate actionpack-3.2.19, because rack-1.5.2 conflicts with rack (~> 1.4.5) (Gem::LoadError)