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

AW: RE: Installing SVN without root access

From: Felix Gilcher <gilcher_at_exozet.com>
Date: 2006-06-20 14:44:55 CEST

jason@subversus.org <mailto:jason@subversus.org> schrieb am Dienstag, 20. Juni 2006 14:15:

> I have never come across any decent (by "decent" I mean well-managed)
> shared hosting service that allows you to run ANY type of server in
> their environment. You should thoroughly read your Terms of
> Service agreement
> before attempting something like this, or you'll likely find
> your account
> cancelled. And there's good logic behind this... your
> attempts to run a
> particular piece of software shouldn't negatively affect the
> performance or functionality of other customer's sharing the same
> server.

Indeed. But strictly speaking svn+ssh does not install a server. There is no deamon constantly running on any port but the svnserve binary gets executed when you open your ssh connection and dies when the connection is closed - this eliminates one potential problem: who gets which port?.

And wether you're allowed to run binaries of any kind on the shared server really depends on the hoster. Here in germany it's quite unusual to even get shell access to a shared server while it seems quite common in the states. I've seen some that allow using shell scripts but keep the right to terminate any process using too much resources without notice. I've even seen shared hosters that allow servers/services in their env, but you must request a port assignement and they reserve the right to terminate any rogue process eating up resources.

Thats said: Yes, it's a good idea to read the terms of service. I would probably ask the hosters customer service bevor attempting such a thing.

> The option you mentioned of using a hosting service that
> specializes in SVN
> is probably the easiest and cheapest solution.

Yes, I figured that as well. The fact that they supported subversion (as well as other SCM systems) was a major point in deciding who I would give my money to (please note that I'm speaking for my *private* webspace, my company does it's own hosting and has it's own dedicated svn server).

> However, if you want maximum control over your environment
> then the cheapest
> solution would be a VPS / VDS, which provides you a fraction
> of the capacity
> of a server, but sandboxes your resources as to minimize
> impact on the other
> customers you're sharing the server with. Plus, this way you
> have virtual
> root access of your sandbox allowing you to configure your system and
> install software at-will.

Well, I'm quite happy that I don't have to do that - because it means that I'd have to take care of updates, bugfixes, config errors were my problem etc. and even though I understand some of that stuff, I'm a programmer and no sysadmin. However, you're still right: At the cost of more work a VPS/VDS offers more flexibility.



Felix Gilcher
Head of IT Development
Exozet Berlin GmbH
Rotherstraße 20
10245 Berlin
eMail: gilcher@exozet.com
URL: www.exozet.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 20 14:46:39 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.