Let's say that I use Rails version 2.3.2 to create a new application
(e.g., "rails my_application"). Later I want to port that same
application to a different server that's running Rails version 2.3.5.
I thought I would be able to just create a tarball of the original
application and re-deploy it on the new server. Apparently not. On
startup, Passenger (I'm running Passenger) complains that the
application requires Rails 2.3.2.
It would seem to be kind of messy to have to create a virgin
application on the new server using Rails 2.3.5, configure it, and
then have to copy all of the old files from the original application
into it. I'm hoping that there is an easier way. Is there?
Thanks for any input.
... doug
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
