> We have three servers, one for development, one for testing, and one
> for production, and I like this setup. It would be impractical for
> each of us to have a local development server setup, because it would
> be way too much maintenance, and not everyone is capable of setting it
> up (e.g., our designer).
>
> I also think it's impractical for us to have to first commit our
> changes to the repository, and then go to the development server and
> check out those changes in order to test them.
>
> I suppose one solution might be to use a post-commit hook which checks
> the repository out on our development server, but how would I do this
> securely?
>
> So, how is this typically handled?
Just a thought: one possibility would be to create a virtual host for each
developer on the development server - that way, Fred can test his changes at
http://fred.internal.example.com, whereas Jim would access
http://jim.internal.example.com, where both are serviced by the same
physical server. This way there is only one central configuration file (so
one person can manage it - and keep all the hosts in sync), but it provides
some isolation, allowing one developer to break things without
inconveniencing everyone else...
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 3 17:16:27 2004