You are right that you should not try to use a repository as your wwwroot.
You /might/ checkout your working copy into a test/development server's
wwwroot, if you really want to version-control essentially everything on
your web server.
Is it bad to commit in order to see a change on a "production" web server? I
would say just the opposite. My guess is that most organizations would
prefer not to have uncontrolled changes to a "live" application. It's hard
for me to see why you would want to version-control some files and then
publish uncontrolled edits of them. Wouldn't you like to be able to retrieve
"the files that were on my web server two weeks ago?" If not, why are you
using source control? I commit changes to my code a lot more frequently than
I deploy code to servers for use by others...
RE: post-commit hook: maybe you should look at build/test/deployment
software such as http://draconet.sourceforge.net/ and
http://cruisecontrol.sourceforge.net/. These can help you if you want a
policy like "deploy upon checkin only if it has been more than an hour since
the last deployment."
-----Original Message-----
From: Michiel van Oosterhout [mailto:michiel1978@hotmail.com]
Sent: Tuesday, September 21, 2004 7:58 PM
To: users@subversion.tigris.org
Subject: Web projects (not the VS stuff) and correct post-commit
Hello,
I'm a newbie on subversion. I want to store webprojects in repositories on a
win2k computer which runs apache with virtual hosts for each website. I
develop on another machine in the network. I am confused how to do this,
because the repository is in a special files (Berkeley DB), so I can't have
that as documentroot. Check out to local, edit, commit. Then a hook on
post-commit to update the repository to the documentroot? That would mean
that for every minor edit I should commit to see the result on the server.
That would be a bit much. Any tips, or FAQS on this? I am not currently
using VS, I use dreamweaver.
Thanks
/M
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 22 06:03:57 2004