On 5/11/07, Simon Large <email@example.com> wrote:
> On 11/05/07, Roel Vanhout <firstname.lastname@example.org> wrote:
> > Simon Large wrote:
> > >> No, if your web hosting account provides you with ssh access there is
> > >> another way: http://subversion.tigris.org/faq.html#paranoid (svn+ssh). I
> > >> would recommend this way because it will give you offsite backups 'for
> > >> free'.
> > > But that surely means that his hosting account has to support running
> > > svnserve, no?
> > Well right after I send this mail I realized that I must have been doing
> > this with CVS and not with SVN because in 1999-2000 I wasn't using SVN
> > yet (I think it was still in beta back then) - but it still works with
> > SVN I think. Reading the link I gave, I understand that you don't
> > actually need to run svnserver as in 'let svnserver bind to a port'; to
> > quote from the link 'This makes your SSH program launch a private
> > 'svnserve' process on the remote box, which accesses the repository as
> > your UID and tunnels the information back over the encrypted link.'.
> There's the rub. Somewhere in ISP space you need to be able to run the
> svnserve process, even if it is SSH doing it for you. If they don't
> support subversion and he can't install any programs, where is that
> going to come from?
> > The link says "A simple option is to use the svnserve server instead of
> > Apache. See chapter 6 in the Subversion book for details. However, if
> > your admins don't want you to run Apache, it's very likely they don't
> > want you to run a custom server process on port 3690 either! So the rest
> > of this answer assumes that your admins are okay with you using an
> > existing SSH infrastructure." and I'm thinking that this is the
> > situation that the OP is in.
> Or are you assuming he wants to tunnel through to his svnserve at
> work? I was assuming he wants to get his own ISP to do it.
> David, can you clarify what you are trying to do?
I don't have access to SSH, I'm afraid.
But what I'm trying to do is just have a history of revisions (in case
I really screw up a page, I can just revert or use a past revision),
and a backup of my code.
Local would be better than nothing, but online would be even better.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri May 11 15:18:22 2007