Looks nice, I haven't read either through, but any chance you could merge this into Installation on Windows or at least write it down in a wiki page a link it accordingly? Thanks!

Good afternoon,

After running ChiliProject for several months, I've run across an issue with mongrel that is going to require me to move to different application server - and my research is telling me that thin may be the best option.

I've run into a problem with the above directions - it works fine up until I try to execute thin for the first time, when I get the following:

> D:\chiliproject\chiliproject-3.1.0>thin -e production -p 3001 start
> >> Using rails adapter
> C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.1.4/lib/bundler/r
> untime.rb:31:in `block in setup': You have already activated rack 1.4.1, but you
> r Gemfile requires rack 1.1.3. Using bundle exec may solve this. (Gem::LoadError
> )
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.1.4/
> lib/bundler/runtime.rb:17:in `setup'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.1.4/
> lib/bundler.rb:107:in `setup'
> from D:/chiliproject/chiliproject-3.1.0/config/preinitializer.rb:30:in `
> <top (required)>'
> from D:/chiliproject/chiliproject-3.1.0/config/boot.rb:42:in `load'
> from D:/chiliproject/chiliproject-3.1.0/config/boot.rb:42:in `preinitial
> ize'
> from D:/chiliproject/chiliproject-3.1.0/config/boot.rb:24:in `boot!'
> from D:/chiliproject/chiliproject-3.1.0/config/boot.rb:137:in `<top (req
> uired)>'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/site_ruby/1.9.1/rubygems/custo
> m_require.rb:55:in `require'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/site_ruby/1.9.1/rubygems/custo
> m_require.rb:55:in `require'
> from D:/chiliproject/chiliproject-3.1.0/config/environment.rb:33:in `<to
> p (required)>'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/site_ruby/1.9.1/rubygems/custo
> m_require.rb:55:in `require'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/site_ruby/1.9.1/rubygems/custo
> m_require.rb:55:in `require'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /rack/adapter/rails.rb:37:in `load_application'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /rack/adapter/rails.rb:23:in `initialize'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /rack/adapter/loader.rb:48:in `new'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /rack/adapter/loader.rb:48:in `for'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /thin/controllers/controller.rb:169:in `load_adapter'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /thin/controllers/controller.rb:73:in `start'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /thin/runner.rb:185:in `run_command'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib
> /thin/runner.rb:151:in `run!'
> from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/thin-1.3.1/bin
> /thin:6:in `<top (required)>'
> from C:/RailsInstaller/Ruby1.9.2/bin/thin:19:in `load'
> from C:/RailsInstaller/Ruby1.9.2/bin/thin:19:in `<main>'

Some more research tells me that this error is related to some of the bundled gems not being available outside of the bundle - but as I am not very experienced with RoR, I'm at a loss as to how to continue.

Any help would be much appreciated.

Kirpal

The fix suggested in the error message is probably the right one. Try running thin with: bundle exec thin -e production -p 3001 start.

Quick explanation: when you run a command without bundle exec, all gems are available to thin and it will try to load the newest installed, this can conflict with the application though if the application specifically requires older versions of gems than the newest installed (the older gems are available too, but can't be loaded because the newest is already there). The Gemfile holds a list of gems and versions the application needs and are known to be working. When run with bundle exec, the environment thin runs in only has those gems described in the Gemfile, thus avoiding version conflicts.

Thanks for the quick response, Felix.

My only issue with using bundler is that I have not (at least in the past 5 days of searching) come up with a way to create a windows service using it. I was able to get mongrel working by including the mongrel_service gem within the bundle, and then creating the service using "bundle exec ...", but since the bundle gem doesn't seem to have any functionality for specifying where to start it, I've run up against a dead end here.

I would stick with mongrel, but there are a couple of issues with it that are forcing me to move.

Thanks
Kirpal

Kirpal Sukumar wrote:

My only issue with using bundler is that I have not (at least in the past 5 days of searching) come up with a way to create a windows service using it. I was able to get mongrel working by including the mongrel_service gem within the bundle, and then creating the service using "bundle exec ...", but since the bundle gem doesn't seem to have any functionality for specifying where to start it, I've run up against a dead end here.

If I understand correctly you can't start a windows service in a specific directory? You can tell bundler which Gemfile to use by setting the BUNDLE_GEMFILE environment variable to the path of the Gemfile.

There are ways to start a windows service in a specific directory (the way that Dies did it with winsw above, as well as a few other options), but what I'm having trouble with is getting the bundle to execute properly when called from outside the native directory.

Just as a test, I tried the following:

set BUNDLE_GEMFILE="D:\chiliproject\chiliproject-thin\"
X:\>"C:\RailsInstaller\Ruby1.9.2\bin\ruby.exe" "C:\RailsInstaller\Ruby1.9.2\bin\bundle" exec thin start -e production -p 3002

Which only produces the following error:

X:/"D:/chiliproject/chiliproject-thin/" not found

Thanks,

Kirpal

I think it takes the path to the file, not to the directory, i.e. BUNDLE_GEMFILE="D:\chiliproject\chiliproject-thin\Gemfile".

Felix,

I feel like we're getting closer - after I experimented a little bit, I found that bundler doesn't like quotation marks in its BUNDLE_GEMFILE path. So after changing my environment setting to:

set BUNDLE_GEMFILE=D:\chiliproject\chiliproject-thin\Gemfile

I was able to start thin using full paths...but only when I'm actually executing it from inside the ChiliProject directory

So while this works perfectly:

D:\chiliproject\chiliproject-thin>"C:\RailsInstaller\Ruby1.9.2\bin\ruby.exe" "C:\RailsInstaller\Ruby1.9.2\bin\bundle" exec thin -e production -p 3002 start
Using rails adapter
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on >or after 2011-11-01.
Gem.source_index called from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/rails-2.3.14/lib/rails/gem_dependency.rb:21.
Thin web server (v1.3.1 codename Triple Espresso)
Maximum connections set to 1024
Listening on 0.0.0.0:3002, CTRL+C to stop

This fails:

D:\>"C:\RailsInstaller\Ruby1.9.2\bin\ruby.exe" "C:\RailsInstaller\Ruby1.9.2\bin\bundle" exec thin -e production -p 3002 start
No adapter found for D:/

BUT!

I also remembered that thin needs a config directory... and modified my command as follows:

D:\>"C:\RailsInstaller\Ruby1.9.2\bin\ruby.exe" "C:\RailsInstaller\Ruby1.9.2\bin\bundle" exec thin -e production -p 3002 -c D:\chiliproject\chiliproject-thin start
Using rails adapter
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from C:/RailsInstaller/Ruby1.9.2/lib/ruby/gems/1.9.1/gems/rails-2.3.14/lib/rails/gem_dependency.rb:21.
Thin web server (v1.3.1 codename Triple Espresso)
Maximum connections set to 1024
Listening on 0.0.0.0:3002, CTRL+C to stop

And have it working from any directory.

Now to figure out how to translate this into a working service, and I'll be all set.

Kirpal

Hello Kipral

I am still on the same road as you are, try to achieve setup "application server" run CP as a windows service, i only achieved to run WEBRick as a windows service for CP explained here http://www.chiliproject.org/boards/1/topics/1420?r=1763#message-1763

Still wondering if it is possible to get run on Tomcat window service, and use of War file to auto deploy CP would be great at Tomcat
but manual deploy will do

i will follow this topic and see if i can help,

figure out how i can delete this double posted reply (otherwise i will re use this reply space), sorry