Rails - Mar 2005 - Ruby on Rails advocacy documentation?

The system administrators for the dynamic web servers at my university
workplace are paranoid and overprotective. I would like to make a case
for requesting them to support Ruby on Rails, but it''s kind of a David
vs. Goliath situation (clever, eh?).

I wouldn''t be asking them to debug my code... I''d just like
for them
to configure their servers so that my code will run.

My question is this: is there some documentation available that
demonstrates the worthiness of supporting Ruby, and especially Ruby on
Rails? If there isn''t already, perhaps a wiki entry/section would help
people like me that do not have the option of simply shopping
elsewhere and using Ruby-friendly companies such as TextDrive.

Thanks,
Bryce

* bryce benton [2005-03-25 10:01]:
> The system administrators for the dynamic web servers at my university
> workplace are paranoid and overprotective. I would like to make a case
IMHO those are generally good traits for a sysadmin to have - those
servers go down, they''re taking the heat, not you! But of course it can
be frustrating to developers.
> My question is this: is there some documentation available that
> demonstrates the worthiness of supporting Ruby, and especially Ruby on
> Rails? If there isn''t already, perhaps a wiki entry/section would
help
> people like me that do not have the option of simply shopping
> elsewhere and using Ruby-friendly companies such as TextDrive.
I don''t have docs to point you to, but here''s one idea:
perhaps they can
deploy ruby/gems on another server for you, and proxy requests for your
rails apps to that server? This way they''ve sandboxed you and any
conceivable problems you could cause (unlikley, but not 0% chance) would
be limited to that separate server. Perhaps after some "due diligence"
time running on a separate "app server" they''d feel more
comfortable
deploying ruby on the (most likley) beefier web servers?


-- 

______________________________
toddgrimason*todd-AT-slack.net