diff options
| author | https://www.google.com/accounts/o8/id?id=AItOawlcaGfdn9Kye1Gc8aGb67PDVQW4mKbQD7E <https://www.google.com/accounts/o8/id?id=AItOawlcaGfdn9Kye1Gc8aGb67PDVQW4mKbQD7E@web> | 2010-05-17 17:31:55 +0000 |
|---|---|---|
| committer | Joey Hess <joey@finch.kitenet.net> | 2010-05-17 17:31:55 +0000 |
| commit | d63553b39b4afb18a5b3ee32131095699582529c (patch) | |
| tree | 670d5e7b0785d8a65a37225ad052e1be16b90395 | |
| parent | eb28db2ad5d38110e7678012aaabce22f89063a2 (diff) | |
response
| -rw-r--r-- | doc/forum/ikiwiki_development_environment_tips.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/forum/ikiwiki_development_environment_tips.mdwn b/doc/forum/ikiwiki_development_environment_tips.mdwn index d0dd01425..9fa3595ed 100644 --- a/doc/forum/ikiwiki_development_environment_tips.mdwn +++ b/doc/forum/ikiwiki_development_environment_tips.mdwn @@ -1,3 +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]] |