I think you could perhaps manage versioning on a separate repository (mercurial comes to mind) via etckeeper or icron. That way, you can track changes Bear in mind that those alterations come on a filesystem level, so you're not able, say, to perform a full audit. If there are logs, it is suggested to keep them as well -- -- Aldrin Leal, <aldrin@xxxxxxxxxxx> / http://www.leal.eng.br/mnemetica/ On Fri, Mar 25, 2011 at 10:15 AM, Guillaume Turri <guillaume.turri@xxxxxxxxx > wrote: > Hi, > > > 2011/3/25 Michael Kirchner <michael.kirchner@xxxxxxxxxx> > >> >> I am trying to use dokuwiki as a electronic laboratory notebook. One >> important requirement is that changes are traceable. >> >> While this seems to work fine within dokuwiki, I fear someone asking me >> "But if someone changes the textfiles directly without using the >> webinterface ..." >> >> What should I answer? Is there a risk? Would a manual edit show traces >> in "older versions"? Is there even a plugin to secure pages against >> manual edits? >> > > With Anteater, if I edit manually a page, I can see it in "old revisions", > and it tells "external edit". > > Therefore, if only a data file is changed, this change can be seen > (although it's not possible to know who made this change). > > Obviously, if someone (with enough permissions on the server) really wants > to make sure his change isn't recorded, I guess it would still be possible, > editing metadata files. But it would be the case with any other software. > To avoid sabotage, the only way is to make sure no one has enough > permissions on the server. > > Regards, > Guillaume >