Collaboration/development: SVN (or the like) on shared hosting?
no2e - June 26, 2009 - 13:20
I want to create a development platform with Drupal. A few friends and me shall be able to collaborate in creating web sites. I think I'll use Project and Project issue tracking.
Now, would it be possible to get a revision control / repository for the code we produce? (everyone is working alone from his home) The problem might be: I only have a shared hosting account (LAMP).
I only know/used SVN before - but afaik you can't install it on shared hosting.
Are the alternatives, that
- work on shared hosting (condition)
- can be integrated into Drupal (no condition)
Or any other ideas how we could collaborate effective?
Hosting with Subversion
Hi,
I think I have seen some instructions on installing SVN on shared hosting, but it involves a lot of fiddling around, and there's no guarantee that the host will allow you to keep the service running. However I noticed recently that OVH have started offering it with some of their shared hosting packages and, as I see you're in Germany, you might want to check them out. I'm not affiliated with them, but I have used them for several projects.
As for getting SVN and Drupal integrated, you might want to look at the http://drupal.org/project/versioncontrol module, if you haven't already, which apparantly integrates with the Project module - but I haven't tried this myself.
Thanks, matkeane.
Thanks, matkeane.
At the moment I can't and don't want to change my host, so OVH would be no solution for me.
Oh, really? I think I'd have no problem with my host (only chats are not allowed). Do you know where to find a guide or something?
----
Are there no other version control systems than SVN, that work on LAMP?
SVN installation
Hi,
At the time, I was using 1and1, and I just googled around for 'subversion install 1and1' and found some instructions that worked... You might find something for your host or, if you have shell access and you can run the 'make' command, you can follow the installation instructions for SVN, which is pretty much what it came down to.
One other thing to bear in mind is that, having SVN on the same server as your web host makes it easy to do neat tricks like post-commit hooks to roll stuff out to your site. On the other hand, having your SVN repos on a completely separate server means that it's in effect an off-site backup should your web server die, so if you had the budget to get some cheap hosting with SVN somewhere else, it wouldn't be a bad idea.
I started using SVN because it was flavour of the month at the time, and supposedly overcame all the disadvantages of CVS. Nowadays you need to be running GIT to keep up with the fashionable geeks!