SubVersion Setups

2 posts / 0 new
Last post
#1 Tue, 10/10/2006 - 01:46
TonyDilado

SubVersion Setups

Greetings,

I have SVN installed and I'm interested in deploying WebSVN and repository setups for each of my Virtualmin accounts. I was curious what the best approach is when doing so. I had planned to simply setup /etc/skel with svn/ containing websvn/ and repos/ and having Virtualmin substitute variables to configure WebSVN specifically for the vhost. Does this seem like a resonable approach?

If you have SVN setup on your virtualmin server, please share with us your arrangement of things.

Thanks, Tony

Tue, 10/10/2006 - 20:39
Joe
Joe's picture

Hey Tony,

There are several possible options for doing what you want to do, and I think you're probably already onto the best choice. Just be sure to enable substitution for the Server Template(s) you'll be using this skel with (this option is in the Home directory section of the template).

I'm not at all familiar with WebSVN (I've only used Trac or ViewCVS with SVN patches), so I don't know off-hand how complex the configuration is. I'm guessing "not very", and so a few substitutions are probably sufficient for your needs.

If you needed something a bit more fancy and clever looking, you could write a Script Installer for WebSVN and then have it automatically setup in each domain (Scripts can be chosen for automatic installation in Server Templates). Script Installers, because they have access to all of Perl and the Webmin libraries, can do just about anything...so if complex automation is needed, this might be the way to go. A Script Installer has access to all of the variables about the domain, as well. But I suspect it'll be overkill for this particular task. Just covering the bases. ;-)

And, if you don't like perl, you could write a script in any language and call it with the "Command to run after making changes to a server". You can pass in the variables on the command line, so it can know what it needs to know about things--but you have to make it quite a bit smarter than you'd need to do with the other options (because the other options are only called on domain creation, whereas this method is called every time a modification is made--so you have to make sure it's a domain creation rather than modification).

As I said, I think you're probably on the right path already. Let us know if you have any problems getting it all to spin.

--

Check out the forum guidelines!