I encountered this today, and it took me some time to figure out what’s going on, as the behavior was so strange it shut off my reasoning.
You’ve got a hosting, neat… a shared one. Now it’d be cool if you could move your subversion repositories there also. But, you can’t just daemonize svnserve or enable webdav in Apache.
SSH is the solution for you. SVN+SSH to be precise. The setup and configuration is pretty straight-forward, but there are quite a few glitches along the way.
All you’ll need for this is SSH access to the server and basic experience with the shell.
Hope this guide will help you: Setup a SVN Server on a Shared Hosting – it took me some time to get over all problems, I hope it’ll save some time to you!
ssh is an extremely useful tool to work remotely and securely on *nix systems.
But the usual password protected access strategy is not the safest way to go; anyone can try to guess your password, use a keylogger attack, etc.
One (big) safety step above is the pubkey (identity) authentication. This uses a pair key-passphrase for remote access.
You can make your system way safer with just 3 simple steps.