Thanks for all the replies, I think i'll take a look at CruiseControl it
Also about the .svn folder, its stupid but I didn't thought about
disallowing this directly from IIS. :P
And Sean, just wondering how would you manage your deploy with svn export ?
If I do a svn export over a current existing copy, if there was old
files in the head copy, basically it won't delete
those files in my local copy. So theorically, I would have to delete
everything then do export ? Or do you have another way ?
Ryan Schmidt a écrit :
> On Jul 27, 2006, at 04:25, Foy, Sean wrote:
>> On Jul 26, 2006, at 23:16, Eric Rousse wrote:
>>> Currently I've did a setup of SVN on a Windows 2000 server, it's
>>> working perfectly fine. That server is currently our dev server
>>> running IIS.
>>> What I did, is that I've installed svnserve on it, and every time
>>> someone does an modification on a file then a commit, via
>>> TortoiseSVN (on their PC). It calls a post-commit hook on the server.
>>> C:\Progra~1\Subver~1\bin\svn update D:\websites\bluffm~1.com
>>> It works okay, but of course, I'm getting all the .svn folders in my
>>> websites, no big deal since its a dev site, but still I'm looking
>>> for other solution, if there's any...
>>> I haven't seen any clear solution and windows based solution about
>>> that... I've heard a couple of solution with perl possibly, and by
>>> using svn export (but in this case we have to find a way to delete
>>> removed files, right ?)
>>> The other problem, is that since the dev ppl, have access to the dev
>>> server via SVN, I was wondering, how we could automate the update of
>>> our prod server easily ? Either via the dev pc by using another
>>> repository to send the stuff to the prod server or with simply a
>>> script on the server it self, that could update the prod one. I was
>>> thinking of maybe a asp page that could call an svn update or export
>>> from the prod server. That way the dev ppl could do a deploy
>> Those .svn directories indicate that you have SVN working copies. You
>> don't want working copies if you don't plan to contribute changes back
>> to the repository from that machine. You can use something like svn's
>> export command to just download a snapshot of the repository contents to
>> a directory so that you can serve up those contents using IIS.
> Sean, using a working copy is a very convenient way to update a
> production web site, and it's even recommended in the FAQ:
> That entry also addresses Eric's concern about the .svn directories --
> you simply configure the web server to deny access to those. The
> example provided is for Apache; for IIS you'll have to consult their
> For deploying to a different server, there are a number of options.
> One good solution is to have the post-commit hook on the repository
> machine connect to the production server via ssh and execute the
> update command that way, e.g.:
> ssh production.example.com svn update /path/to/working/copy
> You can configure SSH so that no username or password is necessary to
> log in, by using public/private keypairs on both machines.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jul 27 14:45:09 2006