I've resisted making web-based management a priority of the OSU server because I feel once the desired configuration is acheived, the bulk of work shifts to maintaining the served content rather the configuration. Even though I don't intend to make web-based managment native to the server, I have made experiments in scripts to help manage the configuration file. It left the syntax of the configuration file exposed, so if it had been developed fully, it would be no better than a language sensitive editor for server configuration files. Uncomment the protect rule, this forces the server to use servermaint.prot to control access to the servermaint script. There are 5 general directives that the server actively executes and an arbitirary number of additional directives for private use by maintenance scripts.
All directives begin with a period.
The completed command is then interpreted as a normal command. Authorizes who can access the configuration file via this script. A configuration file may specify many authorized users.