aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2011-11-30 16:09:09 -0400
committerJoey Hess <joey@kitenet.net>2011-11-30 16:09:09 -0400
commitdf8f87770e4e7607dde9544edcb6cc990b625844 (patch)
treec3f3e3a743ad3b093c5b65a60279396fb4e7f25a /doc
parent0a7264b22717d2e7800ccbe32a636036067b6472 (diff)
downloadikiwiki-df8f87770e4e7607dde9544edcb6cc990b625844.tar
ikiwiki-df8f87770e4e7607dde9544edcb6cc990b625844.tar.gz
thoughts
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/Render_multiple_destinations_from_one_source.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/todo/Render_multiple_destinations_from_one_source.mdwn b/doc/todo/Render_multiple_destinations_from_one_source.mdwn
index 0af5ed172..5fd787607 100644
--- a/doc/todo/Render_multiple_destinations_from_one_source.mdwn
+++ b/doc/todo/Render_multiple_destinations_from_one_source.mdwn
@@ -32,3 +32,19 @@ Alternatively, one might invent a new way of specifying alternative settings. i
where the existance of the <tt>additionalsites</tt> list provokes additional runs through using the settings with matching extra bits to be used to override the defaults found in the rest of the file.
Just brainstorming a bit after [[liw]]'s comment about this being useful on IRC, and thought I'd write the idea up while I was thinking about it. -[[fil]]
+
+> I don't think you can avoid ikiwiki needing to store a different
+> `.ikiwiki` directory with state for each site. Differences in
+> configuration can affect the state it stores in arbitrary ways,
+> ranging from which pages are even built to what plugins are enabled and
+> store state. This also means that it doesn't make sense to try and
+> share state amoung rebuilds of the same site.
+>
+> There is a hidden, and undocumented configuration setting `wikistatedir`
+> that can actually be pointed at a different directory than `.ikiwiki`.
+> Then you can rebuild multiple configurations from one working directory.
+>
+> Another handy trick is to use the old perl-format (not yaml) setup file,
+> and parameterize it using `$ENV{FOO}`, then you can build two different
+> setups from the same setup file.
+> --[[Joey]]