>> From: Adam Lofstedt [mailto:adaml@visimation.com]
I'm trying to move from Dreamweaver/Sourcesafe to Visual Studio.Net and
Subversion. Previously, I used a "shadow" project in Sourcesafe to
mirror the latest version of project files to the web server root
folder. This enabled me to make my changes live on the web server when
I checked in the files.
What are my options with Subversion? How can I, upon check-in, have the
latest versions placed or mirrored in the web server's root?
<<
There are several options, but I'll only concentrate on the one matching
what you're used to.
There is not any direct equivalent of Shadow folders in Subversion.
However, you could have a post-commit scripts that copies the changed
files out to the web server. This is actually better than VSS shadow
folders in many ways:
* Potential for actioning directory renames (VSS won't do)
* You're not limited to a directory in a file system - you could
access the web server via FTP (or WebDAV!!)
* You could get clever and, say, precompile templates or process
includes on the way
* Only the subversion server process needs access to the web server
(VSS requires the shadow folder to be accessible to all users who are
comitting, at least I assume it does since it's a client-only app)
I'm not enough of an expert to write this post-commit script out of my
head, but some may exist already. Something like (pseudocode):
For each (path) in output of SVNLOOK CHANGED
SVNLOOK CAT (path) >(web server path)
End for
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 17 01:58:32 2003