Jeremy Hinegardner
7/3/2008 5:14:00 AM
On Thu, Jul 03, 2008 at 06:14:49AM +0900, Greg Willits wrote:
> I have a project where a number of internally-developed Ruby libraries
> will need to be installed on numerous machines. Small apps will then be
> written using this set of libraries almost like a framework really.
>
> Is it worth considering building a gem out of this library and running a
> private gem server in order to manage these libraries? The alternative
> would be to maintain working copies (maybe in site_ruby?) from an svn
> server -- much like you'd typically maintain a Rails app on servers.
yes, it is always worthwhile to build a gem :-). Its good experience
and something every ruby developer should know how to do. And if the
code is useful outside your specific application it makes it easy to
distribute to the rest of the world.
This is exactly what we do at my job. Currently we have 18 gems that
define our private codebase. We maintain an internal gem server, and
capistrano deployment scripts to manage the installation of the gems on
the various machines depending on their role. Our infrastructure is a
mixture of command line, rails and merb apps, and this approach is
working pretty well for us.
enjoy,
-jeremy
--
========================================================================
Jeremy Hinegardner jeremy@hinegardner.org