SVN access over HTTPS

OrangyTang

Hello! Is there any progress on being able to access SVN over https? I've got a temporary solution hooked up via svn+ssh but due to the way we manage users and accounts that doesn't scale very well. It also makes TortoiseSVN tricker for non-technical users.

Is there any estimated dates? Every time I ask it seems to be put back another month. 🙁

Thanks.

sean

OrangyTang we actually soft-launched that about a week or so ago, ie you can create a Subversion app via the dashboard now and attach it to site.

We've not made the official announcement yet because I've not had a chance to write the documentation for it.

OrangyTang

That's good to hear, thanks!

Since I already have a few (rather large) repositories set up, is there a straightforward way to migrate it across? Can I create a new repository and copy the files across or am I going to have to do a full export/import?

sean

OrangyTang You'll have to do the full export/import, eg:

Export the repo at the source with svnadmin dump.
Create the svn app here.
Transfer the dump over to Opalstack.
Import the dump with svnadmin load.

OrangyTang

Hello! I know the docs are a work-in-progress, but could you touch on how to set up multiple users for https access?

Usually i'd use htpasswd and add users there, but the OpalStack svn seems to ignore that and only use the shell user/password? And if I add shell users, they can't access the new https+svn application so I can't add them to the passwd file. Ideally I'd just use one shell user and multiple htpasswd users, is that possible?

Thanks.

sean

OrangyTang Ideally I'd just use one shell user and multiple htpasswd users, is that possible?

That's exactly what you should be doing for SVN over the web, eg to add new users alice and bob:

cd ~/apps/appname
htpasswd ./passwd bob
htpasswd ./passwd alice

If that's not working for you then please email support for assistance.

OrangyTang

Ahaha, I'm an idiot - I was using htpasswd but it was generating a brand-new .htpasswd file because I didn't realise I should have been pointing it at the existing .passwd instead.

Thanks for the quick response!