Hmmm, a wiki. We do have Twiki, but I don't think there's anyone here (that I know of) who knows how to set up the permissions properly.
Also, since the idea is that it will work in an emergency, it has to be as simple as possible. If I write a CGI script, only two machines have to be up for it to work. Use a databse and that number goes up by 50%. Not sure about the Wiki. Also have to check if we have the DBI::* modules installed. Thanks again for the replies. ++
Terrence
_________________________________________________________________________________
I like computer programming because it's like Legos for the mind.
| [reply] |
My employer was using swiki for awhile, which does not use a database backend - instead it uses xml files. The idea was to keep it as simple as possible and remove dependencies and simplify administration. Worked well until the machine went down because of a runaway script and the XML files were mangled somehow. We have since switched to using a different wiki, with a database backend.
Issues like file/record locking and the ability to gracefully handle an unexpected shutdown are things that databases excel at. I would recommend taking advantage of this.
If the DBI modules are not installed on the server you can always install them to a local directory and define the PERL5LIB environment variable.
As for reducing the number of machines involved, why not run the database on the same machine as the web service?
| [reply] |
| [reply] |