I do much of my development for Barquin on CRuby.   It works most of
the time, but very occasionally we do find a difference between the
two versions.

Also, try out torquebox.   I'm fairly sure it will let you avoid
restarting Java.

Bryan

On Tue, Nov 22, 2011 at 3:35 PM, Ankur <[email protected]> wrote:
> Owen
>
> I was interested in JRuby.  I heard that when developing you need to
> always use JRuby environment to do development.  One cannot use
> Mongrel,etc in development and then seamlessly go to JRuby for
> production?  Mainly because of gems?
>
> How does the extra startup time affect your production?  I only tried
> it on a HUGE application and JRuby was too slow to start.  But for
> normal sized applications is it manageable?
>
> We are using Java code for a Rails app, but we just use Ruby Java
> Bridge gem and it works great.
>
> Ankur
>
> On Nov 21, 1:42 pm, Owen <[email protected]> wrote:
>> Don't forget that JRuby is a proven, reliable, and performant
>> environment for Hobo.
>>
>> All of Barquin's mission-critical Rails/Hobo apps are running on JBoss
>> AS using JRuby.  This also provides the connection to Java libraries
>> we need.
>>
>> For those Microsoft shops out there, we have a high-profile BI
>> application running on Windows Server 2008 Using a Windows version of
>> JBoss) and SQL Server 2008 R2 on the back end.
>>
>> Just an FYI...
>>
>> -Owen
>>
>> On Nov 21, 5:21 am, Drammy <[email protected]> wrote:
>>
>>
>>
>>
>>
>>
>>
>> > I did try rails installer and found it installed Rails 3.1.
>>
>> > Since you asked though I just checked the site a found a latest stable
>> > release for Rails 3.0.1... Thanks
>>
>> > On Nov 20, 1:38 pm, Ankur <[email protected]> wrote:
>>
>> > > Did you try Rails Installer?
>>
>> > > I ran that on Win 7 64bit and it worked great.  I am considering using
>> > > Vagrant thought to just have my environment in Linux though.
>>
>> > > On Nov 20, 3:58 am, Drammy <[email protected]> wrote:
>>
>> > > > Hi all,
>>
>> > > > Veering new to rails and ruby it took me a few weeks to get a good
>> > > > stable installation of hobo working. I made some notes (hence them
>> > > > being past tense) for my own personal reference and thought it may be
>> > > > useful if I shared them.
>>
>> > > > This was to instal hobo 1.3.0pre2 and may need a bit of tweaking for
>> > > > the full 1.3.0 release.
>>
>> > > > Please feel free to comment/improve the process for future users/noobs
>> > > > who may struggle like I did...
>>
>> > > >  1. Installed ruby 1.9.2 p290
>> > > > 2. Downloaded and installed RubyGems 1.8.11 - ruby setup.rb
>> > > > 3. Installed devkit - ruby dk.rb init & ruby dk.rb install
>> > > > 4. Installed Rails - gem install rails -v 3.0.10 --include-
>> > > > dependencies
>> > > > 5. Made sure the only remote resource was rubygems.org
>> > > > 6. Installed hobo - gem install hobo --pre --no-ri --no-rdoc
>> > > > 7. Installed sqlite3 - gem install sqlite3
>> > > > 8. Copied sqlite dll and def files into C:\ruby192\bin
>> > > > 9. Installed earlier version of will_paginate - gem install
>> > > > will_paginate -v 3.0.pre2
>> > > > 10. Add gem dependency to sites gemfile - gem "will_paginate",
>> > > > "3.0.pre2"
>> > > > 11. Unlock the bundle - bundle update will_paginate
>> > > > 12. Do a Bundle Install on the site
>> > > > 13. Uninstall will_paginate version 3.0.pre4 - gem uninstall
>> > > > will_paginate -v 3.0.pre4
>>
>> > > > Cheers,
>> > > > Drammy
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Hobo Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/hobousers?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/hobousers?hl=en.

Reply via email to