Greetings, disclaimer: just installed rubygems, so no pratical experience and only
skim some docs
There has been some questions/comments about how to get ruby ‘accepted’
in your work environment. I was hoping to use the ‘build it and they
will come approach’. I.e. code some utilities to help in job function.
In order to be successful, not only the utilities need to be useful,
but ‘easy’ to distribute. The utilities would be very ‘corporate’
specific. I would not need (and in some cases, not want) them to be
'publicly available. I guess the gem could be ‘distributed’ on a
private system, but then why ‘polute’ the gem ‘index/repository’ with
those entries.
Is is currently possible to create/setup a hierarchy. I would like to
use standard gem commands that would ‘query’ a private server first, but
that could ‘redirect’ the query to the ‘public’ gem site, if query does
not match on the private server.
Hope I am making some sense.
Any pointers appreciated,
Dany
There has been some questions/comments about how to get ruby ‘accepted’
in your work environment. I was hoping to use the ‘build it and they
will come approach’. I.e. code some utilities to help in job function.
In order to be successful, not only the utilities need to be useful,
but ‘easy’ to distribute.
Sorry I can’t answer your gems question, but RubyScript2Exe is another
way to make easily distributable ruby scripts:
Is is currently possible to create/setup a hierarchy. I would like to
use standard gem commands that would ‘query’ a private server first, but
that could ‘redirect’ the query to the ‘public’ gem site, if query does
not match on the private server.
You can specify what URL to use to fetch gems. For your case, you could
set this to a local network URL.
(Some folks already do stuff like this, releasing beta or unstable gems
by hosting them on public, though non-standard, gem server locations. )
I think it is possible to set this in a gem config file so that users
do not have to type it out on each gem install. Or wrap it in script so
that users can more easily opt to install from the local net or the
public gem repositories.
There has been some questions/comments about how to get ruby ‘accepted’
in your work environment. I was hoping to use the ‘build it and they
will come approach’. I.e. code some utilities to help in job function.
In order to be successful, not only the utilities need to be useful,
but ‘easy’ to distribute. The utilities would be very ‘corporate’
specific. I would not need (and in some cases, not want) them to be
'publicly available. I guess the gem could be ‘distributed’ on a
private system, but then why ‘polute’ the gem ‘index/repository’ with
those entries.
Is is currently possible to create/setup a hierarchy. I would like to
use standard gem commands that would ‘query’ a private server first, but
that could ‘redirect’ the query to the ‘public’ gem site, if query does
not match on the private server.