remove web-base-dir which does not make any sense now
svn: r12533
This commit is contained in:
parent
827b76cb6f
commit
aa824d8e05
|
@ -74,7 +74,6 @@
|
|||
[(allow-new-users) (values #f id )]
|
||||
[(allow-change-info) (values #f id )]
|
||||
[(master-password) (values #f id )]
|
||||
[(web-base-dir) (values #f path/false )]
|
||||
[(log-output) (values #t id )]
|
||||
[(log-file) (values "log" path/false )]
|
||||
[(web-log-file) (values #f path/false )]
|
||||
|
|
|
@ -114,16 +114,6 @@ This directory contains the following files and sub-directories:
|
|||
option), or @scheme[#f] for no log file; defaults to
|
||||
@filepath{log}.}
|
||||
|
||||
@item{@indexed-scheme[web-base-dir] --- if @scheme[#f] (the
|
||||
default), the built-in web server will use the
|
||||
@filepath{status-web-root} in the handin collection for its
|
||||
configuration; to have complete control over the built in server
|
||||
content, you can copy and edit @filepath{status-web-root}, then
|
||||
add this configuration entry set to the name of your new copy
|
||||
(relative to the handin server directory, or absolute). Note that
|
||||
you must copy the @filepath{servlets} directory if you want the
|
||||
status servlet.}
|
||||
|
||||
@item{@indexed-scheme[web-log-file] --- a path (relative to handin
|
||||
server directory or absolute) that specifies a filename for
|
||||
logging the internal HTTPS status web server; or @scheme[#f] (the
|
||||
|
@ -218,11 +208,11 @@ This directory contains the following files and sub-directories:
|
|||
|
||||
Changes to @filepath{config.ss} are detected, the file will be
|
||||
re-read, and options are reloaded. A few options are fixed at
|
||||
startup time: port numbers, log file specs, and the
|
||||
@scheme[web-base-dir] are fixed as configured at startup. All other
|
||||
options will change the behavior of the running server (but things
|
||||
like @scheme[username-case-sensitive?] it would be unwise to do
|
||||
so). (For safety, options are not reloaded until the file parses
|
||||
startup time: port numbers and log file specs are fixed as
|
||||
configured at startup. All other options will change the behavior
|
||||
of the running server (but things like
|
||||
@scheme[username-case-sensitive?] it would be unwise to do so).
|
||||
(For safety, options are not reloaded until the file parses
|
||||
correctly, but make sure that you don't save a copy that has
|
||||
inconsistent options: it is best to create a new configuration file
|
||||
and move it over the old one, or use an editor that does so and not
|
||||
|
|
Loading…
Reference in New Issue
Block a user