Hello Matt, On Wed, Mar 26, 2014 at 6:52 PM, Matt Williams <ginol...@gmail.com> wrote: > > Thanks for this information, very useful! The main reason I require the > scripts to be in a network share is I wish to centralise all our scripts. We > have a lot of scripts that report to a monitoring system and they are > executed from countless different servers. It's an administrative headache > trying to manage them. > > With the regard to the post-commit hook, how do you update the "live" > version? Is this via an SVN export?
Not only by `svn export`[1]. You can store a working copy and run `svn update`[2] as well. Depending on the estimated size of all your PowerShell scripts, you may use `svn export` or `svn update` commands. The first one will simply re-download all these scripts from the repository on each commit to the repository (it's not a working copy), the second one can be used if you store a working copy in the share. `svn update` will update the working copy only[3] with changes from the repository thus minimizing the time required to complete the task. Please read SVNBook chapter that describes usage of Subversion hook scripts[4]. NOTE: Hooks run under the same account that runs VisualSVN Server's service. So the account must have enough permissions (NTFS + share) to access the network share in order to be able to export or update the working copy. [1]: http://www.visualsvn.com/support/svnbook/ref/svn/c/export/ [2]: http://www.visualsvn.com/support/svnbook/ref/svn/c/update/ [3]: http://www.visualsvn.com/support/svnbook/tour/cycle/#svn.tour.cycle.update [4]: http://www.visualsvn.com/support/svnbook/reposadmin/create/#svn.reposadmin.create.hooks -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
