Jeff is right here. If all you want is to control your own personal
sources, and not share them anywhere, use file:/// URLs and TortoiseSVN
If you need them accessible across a network or the internet, you must use
svnserve or apache (mod_dav_svn)
Neither of which have GUI administrative controls (or if they do, they
either suck or are expensive)
I would suggest svnserve, its default config files are easy to understand
and customize
On 2/27/07, Jeff Smith <jsmith@robotronics.com> wrote:
>
> On Sunday 11 February 2007 01:15, Christian Buhtz wrote:
> > Jared Hardy schrieb:
> > > The Subversion command-line client installer usually comes with a
> > > usable subversion server option:
> > >
> > > http://subversion.tigris.org/project_packages.html
> > > http://svnbook.red-bean.com/nightly/en/svn.reposadmin.html
> >
> > Sounds very complex. Powerfull but unergonomic.
> > That is why I need an adminastrativ frontend.
>
> You really don't need to go through all that trouble. I am using
> TortoiseSVN on Win XP at another workstation, without any svn server.
> I simply used the menu item "Create repository here..." in Windows
> Explorer to create a repository somewhere discrete, added files to
> it, and then checked out my working copy. It's all done in the
> Windows Explorer GUI, using the Subversion binaries that come with
> TortoiseSVN.
>
> This way, it uses "file://" URLs and does not need the hassle of
> setting up the remote service.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Tue Feb 27 18:09:35 2007