Administration of personal MoinMoin application

See also:

General

• No need to edit configuration files
• No need to deal with encodings, unicode, ~*~ coding ~*~
• No Python code (imports, tabs, spaces, quotes and other trouble)
• No need to restart the server after a configuration change. Either the configuration will be available on the next request or the server is restarted on configuration save.

• All options available, no need to look into code or in HelpOnConfiguration which generally suck.

• Online help for all options, should be enough for most users, including links to HelpPages for hard topics like ACL etc.

• Good defaults that will work out of the box
• Small set of important options, Special options hidden until you reveal them. Similar to today wikiconfig.

The configuration can work like Samba web configuration. You run the server and visit special location like localhost:8008, and submit a form. We can write this using standalone server by adding another webserver listening to the configuration port, or maybe use a magic address like localhost:8000/config, just like we use magic localhost:8000/wiki to serve static files.

Actions available

• Set all farm options
• Create a wiki instance
• Activate/Deactivate a wiki instance
• Set all wiki instance options
• Delete wiki instance? - might be too dangerous
• Maybe in the wiki way - have backup of your config, easy to backup stupid mistakes, maybe using standard bundle code to save configuration revisions?

Make these options available only on the local machine, or make it secure enough to do it from a remote machine. Maybe as the first step, allow only local operation.

Discussion

Just restricting such a configuration dialog to "Personal" editions is quite pointless, having such a thing in the main install is as good as in a PersonalMoinMoin/the DesktopEdition. Other wikis have such a thing already, other webapplications as well.

It make sense to have eaiser administration for the general release, but the general release is based on Python moudles for configuration, which give it unlimited power and flexibility, needed for a server application. The personal version does not need all this power and focused on being easy to use by the general user. Developing admin tool that can work with Python modules and support both edit by hand and edit by admin tool is much harder, therfore, I want to develope a simple solution first. --Nir

• But you have to write an interpreter for the configuration file in any case. I do not see any problem in merging it with the main distribution.
  • No, I don't use or support the current config files at all, its much easier.
    • And where is the configuration stored? Your page talks about a few locations. I mean that by config files.

      • See ../StorageAndPackaging

        • I saw that page. You talk about config files there. And these files need to be read by PMM. --> If you integrate the reader into MM--main, then it can use the config wizard as well.

          • Of course the reader can be integrated, after its done :). Currently its only a very sketchy idea.