1/ Are there any current/future advantages to
using phpwiki 1.2 on Linux with one specific
rdbms? I am trying to choose between the
flavours right now :-)
2/ What mechanisms are available (over and above
the admin LOCK) to defend pages from someone
just attacking the pages you have in your
wiki? I am trying to think of ways to defend
or manage acts of deliberate vandalism or
stupidity on my pages.
3/ What recovery techniques would people suggest
in the event of such an attack or inappropriate
change to a page?
I hope you can help...
If there is nothing in place for 2/ and 3/ above
now I might even start to think of some sort of
contribution to the source :-)
Kind regard,
scf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most (all?) of the PhpWiki developers seem to be using the MySQL backend. In any case, it tends to be the most feature-rich and best tested.
Support for the mSQL backend is probably going to be dropped, so avoid that one.
Anti-vandalism issues.
Currently there is one archived ("back-up") version of each page kept by PhpWiki. The archived version is overwritten each time the author of the page changes. You can easily restore the page to the archived version by following the "EditCopy" link on the "EditPage" page. That's one line of defense.
On the TODO list for the development branch (1.3.x) is:
1. Multiple archived versions.
2. User authentication.
(I'm currently working on #1)
For my wiki, I have a cron script which fetches a snapshot of the entire wiki nightly (using the zip-dump feature of PhpWiki.) The zip dump is unpacked into a directory, and any changed pages are checked into a revision control system. (I use PRCS for this.)
This provides me with daily backups of the wiki which I can use to recover from any serious vandalism (or mistake). (Of which there's been none so far.)
Jeff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sfWiki (http://sfwiki.sourceforge.net) has user auth and single-copy backup/rollback implemented in its CVS tree, and I hope to have a release ready by the end of next week. I'll be watching here to see how the multiple backup copies end up working. :)
-jQuinn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I have three questions:
1/ Are there any current/future advantages to
using phpwiki 1.2 on Linux with one specific
rdbms? I am trying to choose between the
flavours right now :-)
2/ What mechanisms are available (over and above
the admin LOCK) to defend pages from someone
just attacking the pages you have in your
wiki? I am trying to think of ways to defend
or manage acts of deliberate vandalism or
stupidity on my pages.
3/ What recovery techniques would people suggest
in the event of such an attack or inappropriate
change to a page?
I hope you can help...
If there is nothing in place for 2/ and 3/ above
now I might even start to think of some sort of
contribution to the source :-)
Kind regard,
scf
Which backend to use?
Most (all?) of the PhpWiki developers seem to be using the MySQL backend. In any case, it tends to be the most feature-rich and best tested.
Support for the mSQL backend is probably going to be dropped, so avoid that one.
Anti-vandalism issues.
Currently there is one archived ("back-up") version of each page kept by PhpWiki. The archived version is overwritten each time the author of the page changes. You can easily restore the page to the archived version by following the "EditCopy" link on the "EditPage" page. That's one line of defense.
On the TODO list for the development branch (1.3.x) is:
1. Multiple archived versions.
2. User authentication.
(I'm currently working on #1)
For my wiki, I have a cron script which fetches a snapshot of the entire wiki nightly (using the zip-dump feature of PhpWiki.) The zip dump is unpacked into a directory, and any changed pages are checked into a revision control system. (I use PRCS for this.)
This provides me with daily backups of the wiki which I can use to recover from any serious vandalism (or mistake). (Of which there's been none so far.)
Jeff
sfWiki (http://sfwiki.sourceforge.net) has user auth and single-copy backup/rollback implemented in its CVS tree, and I hope to have a release ready by the end of next week. I'll be watching here to see how the multiple backup copies end up working. :)
-jQuinn