bruz / clocky-backend-rails

Rails back end for Clocky, a trivial time tracker with front ends being implemented with different frameworks
http://blog.bruzilla.com
6 stars 2 forks source link

Need help #1

Open mftaher opened 13 years ago

mftaher commented 13 years ago

This might be a stupid, but I'm unable to run the backend server in windows. I have configured with the new Rails version but it gives error when doing the db:migrate. I'm not a ruby programmer so need help to run the rails server for this application. Can anyone help?

bruz commented 13 years ago

What's the error that you're seeing? Could you post the error/backtrace you get when you try running rake db:migrate?

It's been quite a while since I ran this, and when I just tried I got a "uninitialized constant ActiveSupport::Dependencies::Mutex", which is apparently due to an issue with older Rails 2.3 versions and newer versions of RubyGems. I've updated the app to use the latest 2.3 branch Rails (2.3.11) which at least takes care of that problem.

mftaher commented 13 years ago

this is the error I get when I run rake db:migrate

(in C:/Projects/SproutCore/clocky-backend-rails) rake aborted! no such file to load -- initializer internal:lib/rubygems/custom_require:29:in require' <internal:lib/rubygems/custom_require>:29:inrequire' C:/Projects/SproutCore/clocky-backend-rails/config/boot.rb:55:in load_initializ er' C:/Projects/SproutCore/clocky-backend-rails/config/boot.rb:38:inrun' C:/Projects/SproutCore/clocky-backend-rails/config/boot.rb:11:in boot!' C:/Projects/SproutCore/clocky-backend-rails/config/boot.rb:110:in<top (require d)>' internal:lib/rubygems/custom_require:29:in require' <internal:lib/rubygems/custom_require>:29:inrequire' C:/Projects/SproutCore/clocky-backend-rails/Rakefile:4:in <top (required)>' C:/Program Files (x86)/SproutCore/ruby/lib/ruby/1.9.1/rake.rb:2373:inload' C:/Program Files (x86)/SproutCore/ruby/lib/ruby/1.9.1/rake.rb:2373:in raw_load_ rakefile' C:/Program Files (x86)/SproutCore/ruby/lib/ruby/1.9.1/rake.rb:2007:inblock in loadrakefile' C:/Program Files (x86)/SproutCore/ruby/lib/ruby/1.9.1/rake.rb:2058:in `standard exception_handling' C:/Program Files (x86)/SproutCore/ruby/lib/ruby/1.9.1/rake.rb:2006:inload_rake file' C:/Program Files (x86)/SproutCore/ruby/lib/ruby/1.9.1/rake.rb:1991:inrun' C:/Program Files (x86)/SproutCore/ruby/bin/rake:31:in`

'

I have

  • rails version 3.0.7

thanks for the quick reply,

Fazle

On Fri, Jun 3, 2011 at 8:15 AM, bruz reply@reply.github.com wrote:

What's the error that you're seeing? Could you post the error/backtrace you get when you try running rake db:migrate?

It's been quite a while since I ran this, and when I just tried I got a "uninitialized constant ActiveSupport::Dependencies::Mutex", which is apparently due to an issue with older Rails 2.3 versions and newer versions of RubyGems. I've updated the app to use the latest 2.3 branch Rails (2.3.11) which at least takes care of that problem.

Reply to this email directly or view it on GitHub: https://github.com/bruz/clocky-backend-rails/issues/1#comment_1296597

blog: http://ftaher.wordpress.com twitter: http://www.twitter.com/miller107 linkedin: http://www.linkedin.com/in/ftaher

bruz commented 13 years ago

There are some substantial changes to Rails between 2.3 and 3.0, so the newer Rails version is almost certainly what's causing the problem. The quickest fix would probably be to install the older version of Rails that's needed (gem install rails -v=2.3.11) and make sure that the Rails version specified in config/environment.rb is 2.3.11.

I'll have to update this to Rails 3 at some point, which will also have the benefit of using the new dependency manager Bundler to make it easier to ensure you have the right RubyGems for the app.