[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

.svn on the web? Risk

From: Jonathan Powell <Jonathan.Powell_at_augusoft.net>
Date: 2006-02-01 19:46:25 CET

I was wondering if there was a risk to having the .svn folders on your
website. Is it possible to hack into your source code because of this or
are you giving out too much information?
Also I was very curious what model other people are using when you have
three servers, IE dev, staging and live. Currently I was setting this up
The idea was that staging and live would push code when there was a change
from the hook files. The trunk is really all new development and would work
the same way all new commits get pushed out to the server.
Why a push because we don't as developers have access to the live and
staging servers. Also we need to be able to move code at any time to the
servers. The issues I see with this setup are:
    Versions are not tagged or branched as the version #. Also any changes
needed to be pushed out from new development would have to be merged into
those branches (YUCK)... So I am up for suggestions from people out there
that have overcome these hurdles.
The other idea was to have ssh installed on our local machines so we could
pull instead of push code out there then we could move code when we want.
Received on Wed Feb 1 20:11:03 2006

This is an archived mail posted to the Subversion Users mailing list.