On Freund

Touching can be done from the file manager or via FTP. Additionally, weren't there some mention about the possibility of opening up shell access once Charlie is up?

I'm not in a rush as well. BTW, may I suggest using Passenger for RoR deployment on Charlie, rather than mongrel? It's much less of a hassle, and will probably reduce the amount of work you have to put it.

I changed Gemfile.lock to use 1.1 instead of 1.1.5. Can you try again please?

Looks like we're back at the original error For those asking where I see the errors, it's in mongrel.log in the application's log directory.

if you run "bundle show will_paginate" as root in the root of my application's directory it should reveal the location

Still no luck: /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/runtime.rb:27:in `setup': You have already activated mongrel 1.1.5, but your Gemfile requires mongrel 1.1. Consider using bundle exec. (Gem::LoadError) from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in `each'

Fetching source index for http://rubygems.org/ sudo: sorry, you must have a tty to run sudo sudo: sorry, you must have a tty to run sudo I guess I'm going to need you to copy the .bundle or .bundler folder from the root home dir to my home dir and change the ownership to me. Once again, thanks for your patient help!

/usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/resolver.rb:129:in `resolve': Bundler could not find compatible versions for gem "mongrel": (Bundler::VersionConflict) In Gemfile: mongrel_experimental depends on mongrel (= 1.1) mongrel (1.1.5)

As I'm having the same problem, I tried adding those gems to the Gemfile, but it couldn't find mognrel-experimental. When I removed it from the Gemfile, the original problem was still there. Trying to install the mongrel-experimental gem resulted in this: make gcc -I. -I/usr/lib/ruby/1.8/x86_64-linux -I/usr/lib/ruby/1.8/x86_64-linux -I. -fPIC -g -O2 -c fastthread.c make: execvp: gcc: Permission denied make: *** [fastthread.o] Error 127

Let me know if I should open a new thread for this, but I've noticed that even an empty rails app (generated via the rails new command, and nothing else) fails: ** Daemonized, any open files are closed. Look at log/mongrel.pid and log/mongrel.log for info. ** Starting Mongrel listening at 0.0.0.0:12650 ** Starting Rails with production environment... /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.3/lib/active_support/dependencies.rb:239:in `require': no such file to load -- dispatcher (LoadError) from /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.3/lib/active_support/dependencies.rb:239:in `require' from /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.3/lib/active_support/dependencies.rb:227:in `load_dependency' from /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.3/lib/active_support/dependencies.rb:239:in `require' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:148:in `rails' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:113:in `cloaker_' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:149:in `call' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:149:in `listener' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:99:in `cloaker_' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:50:in `call' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:50:in `initialize' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:84:in `new' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:84:in `run' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/command.rb:212:in `run' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281 from /usr/bin/mongrel_rails:19:in `load' from /usr/bin/mongrel_rails:19

OK, so my cron task did manage to run, but it couldn't get the gems, because git is not installed: Fetching http://github.com/mislav/will_paginate.git sh: git: command not found

Thanks. We're almost good. The only problem is the two gems that were installed through GitHub - it seems that bundler installs those into the user's home dir, which would be root, instead of me in our case. I'm guessing that there should be some folder named .bundler or .bundle in root's home dir now. Can you copy it to my home dir and give me permissions? I really appreciate all of your help so far (that goes out to Wizard and jje as well) - this is way better service than I expected for a free host! On second thought, now that most gems are installed, running bundle install through cron will probably do the trick. I'll try that and see if I can manage without further assistance, and will let you know. UPDATE: I've tried to run a cron task - it seemed to have no affect, and I can't access the webmail interface, so I have no way of knowing what happened. Thanks

I'm pretty certain that cron won't be a good idea, can't you su to my user name? (it's onfreund, btw). If not, I guess that running as root might work, but in which case it will install those gems system wide (this actually might be a good idea for at least some of them, such as will_paginate and RMagic).

Basically you need to run "bundle install" (preferably as my user), from the root folder of my rails application (I only have one, the other is empty). Note that one of my dependencies is RMagic, which can be problematic to install (and has a dependency on ImageMagic), and on the other hand is quite popular, so I would suggest installing it system wide if possible, before running bundle install. Let me know if there's anything I can do to help.

The point of bundler is that it allows gems to be installed from different sources (i.e. directly from git-hub) and different versions, and all with a single command. The RubyGems widget of cPanel doesn't seem to support it. Perhaps I can use bundler through a cron task, but: I'm not sure if I'm allowed toI don't know how it will react if it needs user interaction. How are others managing their "problematic" gems? will_paginate, for example, is very common, and the version available in cPanel is not compatible with rails 3.