Allan Swanepoel wrote:
Easy!!
build the subversion repo on the dev web server, in the /var/website
directory, thus, all updated code will be displayed live on the webserver.
And to go from dev to live site, a quick svn co from the live site, and
bob's your uncle.
That will work until you forget to commit something that the site needs
and the test site works but the production one won't. What you really
want is to have everyone who makes changes use their own working copy
(and perhaps their own test server to view it). When they commit, it
should then be checked out to a QA/test location with a test server that
you can trust to only have what it got through the repository. When the
tests there pass, it can go to production, either by updating to the
same revision or tag there, or by using "rsync -C" or some similar means
to copy the tested state to the production location(s). You can use
virtual hosts to combine the development and QA sites if you want, and
the repo can be on the same machine or elsewhere - you'll only access
working copies directly.
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
