|
Thu 16 Aug 2007 08:15:09 PM UTC, comment #13:
Cliss XXI can help you with the Savane installation. If you need information you can mail at contact@cliss21.com, in English.
I'll add an English page about Savane at our website, that'd be useful indeed :)
|
Wed 15 Aug 2007 12:50:49 PM UTC, comment #12:
Like I said -- that website is written entirely in french.... not helpful at all.
They obviously don't want everyone to use them. Just french people.
|
Wed 15 Aug 2007 12:43:32 PM UTC, comment #11:
You can check recipe #219, there's cliss21 that can provide you this service.
|
Wed 15 Aug 2007 12:24:43 PM UTC, comment #10:
I just looked at that file. I think it would be just easier if I paid someone to set my savane up. This is way out of my skills.
Any idea who might want to tackle this?
|
Wed 15 Aug 2007 12:15:18 PM UTC, comment #9:
You would need to edit the savane lib, Savane/Svn.pm
|
Wed 15 Aug 2007 12:06:55 PM UTC, comment #8:
What file do I need to edit to add this in? Savane automatically creates the svn repos so I would need that to be done automatically as well.
BTW the Savane commercial support is nice but that website is totally in french and even trying to navigate it is impossible. Maybe you could suggest that they create a english side as well. I probably would have just had them set my savane up if I could have read anything.
|
Wed 15 Aug 2007 11:35:22 AM UTC, comment #7:
I guess you just have to set up a post-commit command.
|
Wed 15 Aug 2007 11:23:37 AM UTC, comment #6:
What if the svn is on the same box ? How could I use a svn trigger to make the update as soon as the commit is done?
I'm still a relative newbie at svn.
|
Wed 15 Aug 2007 10:48:42 AM UTC, comment #5:
At Gna, the website update is triggered by a cronjob. It must be done so because the website is not on the same system than SVN.
|
Wed 15 Aug 2007 10:45:34 AM UTC, comment #4:
How are you triggering the website update when the user has updated the website/ directory?
|
Sat 06 Jan 2007 07:24:43 AM UTC, comment #3:
FWIW, I created a super-simple hackified shell script to do this:
#!/bin/bash
for each in `ls -1 /var/lib/svn`
do
svnlook tree /var/lib/svn/$each | grep website/
if [ $? == 0 ]; then
if [ -d /var/www/$each ]; then
svn update /var/www/$each
else
svn co file:///var/lib/svn/$each/website /var/www/$each
fi
fi
done
|
Sat 06 Jan 2007 07:00:05 AM UTC, comment #2:
I see. I get it now. Create an Attic, and run a post-commit script to export/update to your homepage document root. Is there any chance an sv_* script has been written to do this, or do I need to do it myself?
|
Fri 05 Jan 2007 06:32:42 AM UTC, comment #1:
Okay, after a bit more hackling, I found the Subdirectory Attic script, and made that work. Any tricks to getting Apache working?
|
Fri 05 Jan 2007 05:59:03 AM UTC, original submission:
I'm working on setting up a Savane instance, and I really like the way Gna! has its subversion repositories set up. I like the idea of managing the project's website from within subversion, as well as managing source code. How do you go about adding that directory? Is it a hack to one of the sv_ backend scripts? And then what's the trick to configuring Apache? Maybe I'm forgetting one key piece of the puzzle, but I can't seem to figure it out.
Savane 3.0+2 on Debian 4.0/Etch
|
Related Recipes:
Savane - Support: sr #1425, Subversion configuration