> >1) I noticed at swiki.net that they had implemented the ability for
> >administrators to "roll back" pages to a previous version, i.e. replacing the
> >current version with an older one. Is this custom-built functionality, or is
> >it part of an admin package that I did not download?
This is a custom swiki.net thing. They diverged from my code fairly
quickly, so they are not very compatible.
> >2) Could someone give me a basic tutorial of where files are located on the
> >server relevant to a given swiki? Essentially, I'm interested in how I might
> >automate a nightly archive solution - what directories do I need to save, do I
> >need to do anything in particular to restore? I had thought I could just copy
> >and restore the files in the "swikiname" directory, where the pages, rendered,
> >and upload directories are, but when I tried copying and restoring, it wasn't
> >very successful -- I assume that there's more information stored somewhere
> >that I neglected to copy over. Or is it necessary to stop the server while
> >restoring?
You do have to stop the server before restoring, but otherwise copying
the "swikiname" directory is the right move.
> >3) Does the Comanche Swiki run headless as well? I've seen instructions for
> >getting the PWS going in a headless run of Squeak on a Linux machine, and was
> >wondering if anyone has successfully done this with a Comanche version.
> >Ideally, we wouldn't need to start up X to get our server up and running in
> >the event of failure.
Yes. You just have to pick up a headless version of the VM. You can
download a headless Linux VM from
http://www.prism.gatech.edu/~gt4510b/work/cs/Squeakh
> >4) Any suggestions on how to begin customizing the Swiki's functionality?
> >Once I become literate in Squeak, is it fairly easy to begin playing around
> >with the Comanche/Swiki code to tweak things? Here are some things that I've
> >thought would be nice:
> > * configuring look/feel beyond the existing templates
> > * admin tools to quickly save/restore pages and/or entire swikis
The first step is to use the inheritance functionality, but you can also
just fool around with things and see how they work, before going and
trying to implement something major.
Peace and Luck!
Je77
