i’d like to share some feelings of mine after a couple of weeks
intermittent attempts to have rails applications working on windows
(XP) with fastcgi performances under apache (2.0).
i’d say the software stack i’m using now will be fairly common as more
and more new rails developers will join the bandwagon.
what is stunning me is the fact that, even if i’m certainly not a
guru, i can’t say i’m a computer illiterate, and notwithstanding this
i’m still struggling just to have an application of mine or, for
example typo, being deployed on the most convenient platform i’ve on
hand (i’m not saying it is the best or the greatest, i’m just say it
is the one i’ve on hand …) after roughly two weeks of efforts.
i checked almost all posts and wiki entries on this subject, founding
several of them somewhat discording and, unfortunately not definitive.
as a matter of fact even if supposedly definitive articles do exists,
if you browse through the end of it you’ll find other people still
struggling with the very same issues i’m still facing, yet unresolved
interestingly enough, i’m not even able to see typo (the rails-based
blog program) running successfully under a fcgi environment (i even
attempted to have lighttpd runs under windows in order to have typo
running, but that is another nightmare …)–btw, it works ok under
a final consideration: rails is great and fun to program, until you
are going to deploy it … this segment of the stack really badly
needs to be documented, explained in details (“why is something
happening on this stack and not on this other one …”), and
effectively covered for the vast majority of deployment cases,
otherwise rails will be, for the foreseeable future, just a promise in