aboutsummaryrefslogtreecommitdiff
path: root/doc/post-commit/discussion.mdwn
blob: 31347a614b9e52f3dcaa8fc0c69b72d5d82183d5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
Hi Joey and many thanks for your work on ikiwiki, as usual you give us a very good soft...

I want to be able to edit my website from a navigator (with the CGI) and
from my favorite editor on my laptop. I have managed to use the subversion wrapper
so I have write a post-commit hook with : 

    cd /~/wikisrc/ 
    svn up
    /usr/bin/ikiwiki --setup ../ikiwiki.setup

at the end.

This configuration works for me, the svn wrapper doesn't seems to
do the svn up stuff so I wonder if I've missed something...

Regards.

> Well, you've created a post-commit script that runs ikiwiki in setup mode.
> That's not how it's generally done, instead you generally configure
> ikiwiki to generate a post-commit _binary_ that runs ikiwiki in update
> mode. That binary can be installed directly as the post-commit hook, or
> called from an existing post-commit hook script, and it will handle the
> necessary svn up, and will update the wiki much quicker than your --setup
> command above (which rebuilds the entire wiki and all wrappers each
> commit)!
>
> In this wiki's setup file, I configure ikiwiki to generate a post-commit
> wrapper binary like so:
> 
> 	wrappers => [
> 	{
> 		wrapper => "/srv/svn/ikiwiki/hooks/post-commit",
> 		wrappermode => "04755",
> 		notify => 1,
> 	}
>	],


Hello, I've setup ikiwiki with subversion. I can edit pages from web browser using CGI and, when I go to recentchanges, it shows that modification with "web" word. But, if I modify any .mdwn file, it gets updated in website but it doesn't show in recentchanges entry with "svn" word. If I run "svn ci -m changes", it shows in recentchanges correctly.

So, I think I miss something, because I don't think I must run "svn add" or "svn commit" anytime I modify or create a wiki file.

Thanks

> Yes, ikiwiki does expect you to use your revision control system to check
> in changes. Otherwise, recentchanges cannot work right, since it uses the
> commit history from your revision control system. --[[Joey]]