Joe,
AFAIK, IIS won’t proxy like Apache can, so I don’t think IIS is the way
to go. SQL Server is supported, but less ideal for Rails. The first
thing I would look into is Mongrel and its Windows service capabilities.
This handles the HTTP side. Apache 2.2.3 does run on Windows, as does
MySQL and PostgreSQL, so you may be able to prove the commercial support
behind MySQL and PostgreSQL and the market dominance of Apache - at
least these are not horriffic hacks, they are normal Windows installs
and work great.
Does this org use any Linux or *BSD systems for email, NFS/Samba file
storage, or firewalling? If this is OK for their IT department, you’ve
won half the battle. If not, they are totally drinking the koolaid and
not realizing that their tech choice was bought by vendor marketing
rather than driven by a very smart developer community (with some big
name converts!).
So, Mongrel or Apache+Mongrel for web, SQL Server for DB - give it a
shot. If they are watching the industry as they should be, they see the
Ruby/Rails tidal wave coming. If you can get them to allow a small
internal project, that’s your foot in the door, so to speak.
I work in a mostly MS shop (some Linux, some Java) but the powers that
be know Rails is making a huge splash. It’s two years old, so it’s not a
‘fad’ anymore.
If all else fails, check out http://www.castleproject.org/ and its
MonoRail and ActiveRecord projects - Rails-like development in .NET. Or
get a different job.
Sorry for the rant - need sleep. Zzzz.
Cheers,
Kevin
Joseph A. wrote:
I work at an organization that is very wrapped up in Microsoft products.
I
am trying to get a test application put in however I’m not sure what to
do
about the infratstructure. If it were up to me we would put in MySQL
and
Apache or Lighty, however its not up to me. The easiest way to get an
application into production at our company would be to use the existing
MS
SQL server and IIS infrastructure. Does anyone have experiences with
this?
If its relatively easy then I will suggest we go with that. However, if
its
more trouble than its worth, I’ll suggest we put together a more
traditional
Rails environment. Thoughts? Suggestions? I appreciate any advice.
Joe