diff options
| author | https://launchpad.net/~beaufils <beaufils@web> | 2015-06-01 08:34:45 -0400 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2015-06-01 08:34:45 -0400 |
| commit | e1e3116b6ae10c72030dc9698a0fc8a84f4252e0 (patch) | |
| tree | e03bd8a018f0aa3ac0c6879e3977d9f581dd7c38 /doc/tips | |
| parent | 91765ab41679f8a066df1a0f85d08e613a4d4a45 (diff) | |
| download | ikiwiki-e1e3116b6ae10c72030dc9698a0fc8a84f4252e0.tar ikiwiki-e1e3116b6ae10c72030dc9698a0fc8a84f4252e0.tar.gz | |
mutiple setup not possible
Diffstat (limited to 'doc/tips')
| -rw-r--r-- | doc/tips/laptop_wiki_with_git/discussion.mdwn | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/tips/laptop_wiki_with_git/discussion.mdwn b/doc/tips/laptop_wiki_with_git/discussion.mdwn index 16e481383..b44285d5c 100644 --- a/doc/tips/laptop_wiki_with_git/discussion.mdwn +++ b/doc/tips/laptop_wiki_with_git/discussion.mdwn @@ -23,3 +23,7 @@ Managing two setup files (one for the server and one for the laptop) is however One solution is to allow multiple use of `--setup` on the command line : the first is the main setup file (the one from the server, e.g. `main.setup`) and the second is the specificities of the laptop clone (e.g `laptop.setup`). In such a situation ikiwiki is called with `ikiwiki --setup main.setup` on the server and `ikiwiki --setup main.setup --setup laptop.setup` on the laptop (merging both configuration data in order). This solution seems to work, but are there any bad side effects which I miss doing that (I thought that in IkiWiki code only one setupfile is keeped) ? --[[bbb]] + +Unfortunatley that does not fully work, as soon as `cgi_wrapper` is defined in setup file since each time ikiwiki reads a setup file it adds (not replace) a wrapper in `$config{wrappers}`. + +I am still trying to find an idea to share config data through server and laptop. --[[bbb]] |