D
Dany Cayouette
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
*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