This is a static dump of issues in the old "Flyspray" bugtracker for DokuWiki. Bugs and feature requests
are now tracked at the issue tracker at Github.
Closed
Won't implement
FS#2008 Use Git as backend
Backend
2010-08-11jkufner
Use Git as backend for storing texts and all uploaded files.
Why?
It will drasticaly extend features and posibilities of wiki engine.
It will be possible to connect two instalations of Dokuwiki and let the second be a snapshot of the first one. So documentation team can prepare documentation for new version of some product and, when time comes, publish it with single click.
It will be easy to manage history of all files, not only texts.
Almost no need for debuging storage itself -- git is already very stable. Only PHP API may need some work.
Probably faster backend and lower disk usage, especialy with larger and older wiki.
Git's branches can act as "editable snapshots" -- almost no work for this nice and powerful feature.
...
How to implement it?
Just make /data/pages a git repository and run "git commit filename.txt" after every change in this file.
Recent changes, diffs, logs, ... all these features should be realy easy to reimplement (call git, show result).
By "Call git" I mean calling appropriate functions via it's PHP API, not calling /usr/bin/git itself, but it can be first (ugly) step.
...
Yes, it is huge and deep change, but i would be great!
Git or Mercurial, git is probably easier. Check out Fossil too, SQLite's SCM (it has a wiki integrated, but it pales in comparison to DokuWiki - maybe the two could merge?)
Anyway, anything with a wider userbase is better - even SVN should be considered a possibility. Something parsable and portable is key.
BUT!!! Make sure you keep the current method as well, it works! Just add on easy flexibility for the SCMs. Possibly a plugin?