Forum: Ruby on Rails Rails setup for multi-user environment?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Christopher J. Mackie (Guest)
on 2006-01-05 23:33
(Received via mailing list)
Is there a way to set up rails on a shared server so that multiple
developers don't each have to install their own copies? We've got an
(internal) shared-hosting server to which I want to add rails, but I'm
not even sure it's possible, much less how to do it.

Basic scenario (machines are Linux):

1 - scripting server, serves PHP and perl via Apache. Developers have no
direct access: they just put their code in their own "magic" folder on
our NAS and the server runs it (as, e.g.,
http://server/my_magic_folder/myscript.php). We could add ror here to
publish rails apps using the same kind of scheme, but they won't let
developers SSH in and run rake or irb.

1 - application server. The "magic" scripting folder is mapped as the
developer's home directory, and this server allows interactive work.
This is how developers who want interactive perl or PHP get it: they use
copies of the languages on this server from the console.  We could put a
copy of ruby/rails here and share it, if rails can be shared.

1 - NAS (fileserver). where all the developer source-code lives. Can't
install apps here.

Our server admins are smart folks, but they're busy and they don't know
(or care) much about rails. I need to be able to show them that adding
rails support is feasible and not too difficult, and give them a clear
idea how to proceed.  Can anyone recommend any solutions and/or point to
any instructions?

Thanks, --CJ
Tom M. (Guest)
on 2006-01-06 00:03
(Received via mailing list)
One of the *very best* things about Rails is that it's SO EASY
to locally install Rails so that there's zero contention for
development resources such as application instances, DB
instances, etc.

Combine with source control, and you have genuine distributed
development the way it should be.

P.S.  Your code will be more easily deployable if you let each
        developer install it at the location of their choosing, and
        NOT at the same location on each development box. This
        will guarantee that no absolute references to resources
        exist in the code.

--
-- Tom M.
This topic is locked and can not be replied to.