Re: SVN Files in Productionenvironments

On Friday 25 November 2005 10:05 am, Greg Thomas wrote:
> On Fri, 25 Nov 2005 16:56:37 +0100, Michel Zobel <zobel@hnw-online.de>
>
> wrote:
> >So my first guess would be to protect the .svn directories via apache
> >htaccess and virtualhost.conf.
> >
> >What else could/should i do?
>
> Checkout http://subversion.tigris.org/faq.html#website-auto-update
> which covers it.
>
> >If not i would just delete all directories named .svn. Ist there a way
> >to checkout without the .svn directories? just the plain code.
>
> Sure - just use "svn export". Though this loses you the ability to do
> a "svn update" to get the latest version.
>
> HTH,
>
> Greg

        We also have a website that uses SVN for version control. We have the live
server running from the "trunk", instead of a tag, due to the frequency of
updates. Keeping that in mind, I'd like to point out that the
afore-mentioned FAQ
(http://subversion.tigris.org/faq.html#website-auto-update) makes the
assumption that the repository and the referenced website exist on the same
machine: in our case, the repository exists in an internal network, whilst
the live server exists in the public network. Thought it might be pertinent.

-- 
Best Regards,
Dan Falconer
"Head Geek",
AvSupport, Inc. (http://www.partslogistics.com)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org