urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'master' of ssh://git.ikiwiki.info/srv/git/ikiwiki.info

master
Joey Hess 2010-05-17 15:42:44 -04:00
parent 5e51560574 f864b74859
commit a5f0fc4931
2 changed files with 37 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/forum/ikiwiki_development_environment_tips.mdwn 100644
View File

@ -0,0 +1,5 @@
I haven't settled on a comfortable/flexible/quick development environment for hacking on ikiwiki. The VM I host my web pages on is not fast enough to use for RAD and ikiwiki. For developing plugins, it seems a bit heavy-weight to clone the entire ikiwiki repository. I haven't managed to get into a habit of running a cloned version of ikiwiki from it's own dir, rather than installing it (If that's even possible). The ikiwiki site source (source ./doc) is quite large and not a great testbed for hacking (e.g. if you are working on a plugin you need a tailored test suite for that plugin).
Does anyone have a comfortable setup or tips they would like to share? -- [[Jon]]
> I've just been setting `libdir` in an existing wiki's setup file. When the plugin's in a decent state, I copy it over to a git checkout and commit. For the plugins I've been working on (auth and VCS), this has been just fine. Are you looking for something more? --[[schmonz]]

32
doc/todo/multiple_template_directories.mdwn
View File

@ -13,3 +13,35 @@ ought to do the trick.
> considered [[done]]. > considered [[done]].
I have a use case for this, a site composed of blogs and wikis, templates divided in three categories : common, blog and wiki. The only solution I found is maintaining hard links, being able to have multiple template dirs would obviously be better. -- Changaco I have a use case for this, a site composed of blogs and wikis, templates divided in three categories : common, blog and wiki. The only solution I found is maintaining hard links, being able to have multiple template dirs would obviously be better. -- Changaco
> [[plugins/underlay]] used to allow adding extra templatedirs, but Joey
> removed that functionality when he made templates search the wiki's
> own `templates` directory.
>
> You can get a 3-level hierarchy like this:
>
> * instance-specific overrides: $srcdir/templates
> * common to the entire site: a directory that is the value of all
> instances' `templatedir` parameters
> * common to every ikiwiki in the world: /usr/share/ikiwiki/templates
> (implicitly searched)
>
> (by "instance" I mean an instance of ikiwiki - a .setup file, basically.)
>
> For a more complex hierarchy you'd need the old [[plugins/underlay]]
> functionality, i.e. you'd need to (ask Joey to) revert the patch that
> removed it. For instance, if anyone has a hierarchy like this, then
> they need the old functionality back in order to split the template
> search path for the things marked `(???)`:
>
> every ikiwiki in the world (/usr/share/ikiwiki/templates)
> \--- your site (???)
> \--- your blogs (???)
> \--- travel blog ($srcdir/templates)
> \--- code blog ($srcdir/templates)
> \--- your wikis (???)
> \--- travel wiki ($srcdir/templates)
> \--- code wiki ($srcdir/templates)
>
> This looks pretty hypothetical to me, though...
> --[[smcv]]