I have an app that is in rails 2.3.10 on my server, the author does not develop it anymore but changes are forbidden due too licensing. On the other Hand I am a rails 3 app that should run under the same server.
First try was to install rails 2x and 3x side by side but that is resulting in various errormessages flooding my logs in both applications.
Given is Apache 2.2 with an 3 month old passanger, ruby 1.8.x, rails versions as stated above.
Is there a way to have the applications work in paralel or have I to backport my own app to rails 2?
I have root access to the server it self, but as already said the application is not under active developement any more and I cant modify it because of the licensing. Porting it would take way to much time too.
I have an app that is in rails 2.3.10 on my server, the author does not
develop it anymore but changes are forbidden due too licensing. On the other
Hand I am a rails 3 app that should run under the same server.
They should have different subdomains, resulting in oldapp.example.com and
newapp.example.com. But how can I achieve this behavior?
First try was to install rails 2x and 3x side by side but that is resulting
in various errormessages flooding my logs in both applications.
Given is Apache 2.2 with an 3 month old passanger, ruby 1.8.x, rails
versions as stated above.
Is there a way to have the applications work in paralel or have I to
backport my own app to rails 2?
I have root access to the server it self, but as already said the
application is not under active developement any more and I cant modify it
because of the licensing. Porting it would take way to much time too.
Multiple rails versions is fine. If you're not already using bundler
then you should as it solve some of the slightly sticky dependency
issues you can run into.
You can install multiple Ruby stacks on the same machine using RVM.
(Ruby Version Manager) However, to run more than one version of
Passenger, you'll have to fire up another instance of your web server
and use a proxy pass. Excerpt from
http://rvm.beginrescueend.com/integration/passenger/:
Q: Can I run multiple projects under passenger with each project on a
different ruby version?
projects under *one* ruby. You can get this behavior using a proxy
pass.
I'm not sure, however, what the repercussions of running Passenger
under one version of Ruby and a project under another. With an RVM
based installation, Passenger is running in an isolated stack with
it's own gems, etc. The apache config points to that stack. Unless
someone chimes in and shoots it down, I would think it's worth a try.
Have you looked into RVM? http://rvm.beginrescueend.com/rvm/basics/
Have you looked into hosting your new site somewhere else? Heroku is
free for smaller sites. If you have a large data requirement you can
use Amazon S3 for about 0.15 / GB / month.
I use RVM in development and it is a great tool, but I am curious… If passenger can only run “one” ruby what is the advantage of installing RVM in the server? Can you create gemsets?
I use RVM in development and it is a great tool, but I am curious.. If
passenger can only run "one" ruby what is the advantage of installing RVM in
the server? Can you create gemsets?
Passenger only wants one ruby interpreter - multiple gemsets are, I
believe, fine (although bundler solves that problem very well too).
RVM does make it really easy to handle ruby version upgrades and that
sort of stuff or if you want a specific version of ruby that isn't the
default one for the distro you use. You can have multiple ruby
versions with passenger, but you need (effectively) several different
passengers running, each with its ruby version (via the passenger
standalone stuff that is mentioned in the page Dan links to)
I am using rvm for developing already bit did not know that I could use it for production as well. I will take a look at your link when home.
I took a look already to heroku, but as far as I could see it would get to expensive, since I had to buy some of the plugins to make the application reachable under my own domain. Neither the old nor the new one are allowed to change the already existing/planned URL. For the existing one it is obvious, the new one is going to be called via another site and the URL is already hardcoded several times and the maintainer refuses to change that.
But I will take a deeper look into heroku options as I am already using it for version controll backup from the github repo and a kind of post-developement-pre-production-environment (“staging” as I have understand so far) without any options that I have to pay for.