This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]
  • Authentication Database (PostgreSQL)
    • User and group tables
    • Authentication configuration
    • Servlet container realm configuration
  • JSPWiki Application
    • Directory layout and permissions
      • WAR file
      • Wiki pages
      • Wiki logs
  • Optimizations
    • Connecting Apache 2 to Tomcat
    • Serving static content from Apache
    • Pre-compiling JSPs
    • Running Tomcat & JSPWiki with a Security Manager
  • Deployment tools
    • SSH agent
    • Ant scripts

This is just a rough outline. I will be fleshing this out over the next few weeks. -- Andrew Jaquith

Comments and Discussion:#

(starts here...)

Operating system and servlet container #

Host access #

Directory layout #

Runtime security #

Runtime users #

Startup scripts #

Authentication #

Container-managed authentication #

Service minimization #

Tomcat hardening #

File permissions #

Servlet logs #

Servlet configuration directory #

Host-based firewall #

IPTables example #

PostgreSQL Database #

User and group tables #

Authentication configuration #

Servlet container realm configuration #

JSPWiki Application #

Directory layout and permissions #

WAR file #

Wiki pages #


At what level do you want this documentation? For programmers? For sophisticated, middle level or novice users?

Would it include things like how to put the jspwiki.properties file back into the war file so that the changes become active.

Note, I'm still learning, but from the LinuxInstallJBOSS page, it seems to me to have the changes to the properties file take affect you need to put them back in the war. Is this correct? Would this kind of knowledged be assumed on this type of page?

Here is another question? How do you update the war in a MS-Windows system? And, should this kind of info be on the page? If not, is it worth having a documentation for users that may want to use the wiki but do not work at these levels?


As I read JSP Wiki Plugins more today I noted you do have levels:
  • content authors
  • template developers
And from the JSP Wiki Documentationpage
  • users
  • administrators-site maintainers
  • developers

What other titles/levels do you use?


Also as you move forward on documentation, reading http://doc.tikiwiki.org/tiki-index.php?page=Collaborative+Documentation%2Cnl&highlight=structured%20doc may be of help.

A main point on that page is:
A real need for structured documentation
Despite the joy and happiness tiki hackers demonstrate in the chaotic fertility on tikiwiki.org, there is a real need for a real classic linear documentation for easy reference. Many tiki contributors asked for a direction where they can help, and the fact is that such collaborative documentation work requires a strong focal point so people can work in effective synchronicity.

One of the strong points of JSP is that it is not chaotic. Your category idea is quite helpful. I'm just pointing out what tiki ran into and wondering if a further level of structure would help?

--Anthony Petrillo, 16-Apr-2006

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
xml
build-library.xml 11.1 kB 1 20-Apr-2004 03:11 66.167.248.121
html
index.html 42.4 kB 1 14-Jun-2007 18:01 220.227.68.5
« This particular version was published on 16-Apr-2006 04:53 by Anthony Petrillo.