J,
> Every time I see this I wonder why Apache/Windows is such a black sheep.
I don't have any problems with Apache on Windows per se. I've certainly run
it before in other situations.
> Everywhere I've worked
> as a web developer (ASP, JSP, PHP, etc over the last ~10 years), we've
> actively used local environments configured to emulate production
> environments, done our development or changes in those local
> environments, committed the changes to the repository and published to a
> development/test server from the source code control tool.
That's exactly how we do it ... for people running Linux. But I can't
possibly configure a Windows environment to emulate our production
environment, because our production environment runs on Linux. There are just
too many differences to attempt to account for. It would be different if the
code and configuration had been designed from the beginning to be platform
independent, but it wasn't; it's never needed to be.
And even if the code would run without change under Windows, this would
necessitate someone installing Perl, Apache, and mySQL (at least the client)
on Jen's local machine. And, as I say, we have no real sysadmin here, so
everyone here is responsible for their own machine. I can't expect Jen to
maintain all that configuration stuff. Plus occasionally we change the
configuration (primarily to add new Perl modules, but sometimes for other
things as well); on Linux, this is all scripted and for Jen's Linux
environment I can just rerun the build script for her. On Windows, she'd have
to update all those things by hand, herself.
I just don't see that it's practical in this particular instance.
-- Buddy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 10 00:13:57 2005