Ruby/Rails support in Virtualmin

Submitted by john.tilghman@g... on Tue, 11/24/2009 - 13:20

I have been having problems with ruby/rails and vm. I was wondering if support for:

http://www.rubyenterpriseedition.com/

and

http://www.modrails.com/

Could be added as I think it might be more stable and not such a moving target.

I need ruby and rails and this looks like a great option, but virtualmin does not support it.

Just a thought.

Thanks, JT

Status: 
Closed (fixed)

Comments

Joe's picture
Submitted by Joe on Tue, 11/24/2009 - 13:29 Pro Licensee

We're planning mod_rails support soon.

I agree that it would be preferable to the current Mongrel stuff. We've never really liked Mongrel, but at the time it was the de facto best practice for deploying RoR apps.

Submitted by john.tilghman@g... on Tue, 11/24/2009 - 14:51

Well I didn't mean just mod_rails.. I mean the ruby that goes with it.

So, can I be a test case for mod_rails support ? :)

JT

PS - I am dying here as I need to deploy RoR sites but I love VM...

Submitted by JamieCameron on Tue, 11/24/2009 - 17:42

I've found using Mongrel to work pretty well, and it is fully supported in Virtualmin.

Did you run into any issues with running Rails apps under Mongrel ?

Submitted by john.tilghman@g... on Tue, 11/24/2009 - 19:13

If you look in the tickets you and I have been trying to get this to work on CentOS.

I am tried of chasing packages for CentOS and just NEED it work.

This other option seems to work, but I cannot manage it from within VM.

You were the one who told me that ruby was difficultto support due to the packages and such.

So I find an option that works, which you do not support and now you say the VM option I have works fine.

But it doesnt. So where do I go ? Maybe ISPconfig or do it by hand.

I paid money for VM becuase I believe it be a good product. And yet I cannot use it for what I need.

If you need remote access to the system to figure this out, fine. If I need to work all my ruby sites by hand, fine.

I just need to know what to do with this.

JT

Submitted by JamieCameron on Tue, 11/24/2009 - 19:19

Sure, I'd be happy to login and take a look at this. My email is jcameron@virtualmin.com .

Also, which was the other ticket you had open?

Submitted by JamieCameron on Wed, 11/25/2009 - 00:36

Ok, I see the problem, and was able to install Rails.

The issue was that you seem to have a different version of Ruby installed from the CentOS default, which is putting Rails apps under /opt/ruby-enterprise/bin . Once I added this directory to the Webmin search path at Webmin -> Webmin Configuration -> Operating System and Environment, I was able to install Rails using Virtualmin just fine.

Submitted by john.tilghman@g... on Wed, 11/25/2009 - 08:17

Yep, I did add that. The reason being is that I could not get it to work with the ruby that comes with CentOS by default.

I could not find all the rpms needed to make the default ruby work. You are welcome to disable the other one and try to make the default one work.

JT

Submitted by JamieCameron on Wed, 11/25/2009 - 10:25

Actually, the installed ruby looks fine to me - I just had to configure Virtualmin to properly detect it.

So does Rails look like it is working OK for you now?

Submitted by john.tilghman@g... on Wed, 11/25/2009 - 17:52

For the most part.. but when I go to http://home-lan.homelinux.com/rails/

But when I click "About your application’s environment" I do not get the screen I should be getting

which means something is still messed up..

JT

Submitted by JamieCameron on Wed, 11/25/2009 - 18:00

Did you re-install rails? If so, did you select the "development mode" option when installing? That page about the environment only appears when development mode is used.

Submitted by john.tilghman@g... on Wed, 11/25/2009 - 19:30

Didnt know that... Let me try that...

Sweet.. All looks good..

Thanks..

Now get to work on that mod_rails support... :)

Really thanks for the help..

JT

Submitted by JamieCameron on Thu, 11/26/2009 - 00:21

Cool .. I will close this bug then.

Submitted by Issues on Thu, 12/10/2009 - 13:20

Automatically closed -- issue fixed for 2 weeks with no activity.