Nanoweb is a very flexible HyperText Transfer Protocol (HTTP) server,
which is fully implemented in the
scripting language and comes along with a bunch of extension modules.
Instead of invoking nanoweb.php directly you should consider utilizing
to get it run as standalone server, alternatively you could just add an
entry to the internet superserver
configuration file to have it automatically started on incoming requests.
-c nanoweb.conf, --config=nanoweb.conf
This tells nanoweb which configuration file to use; if the
is omitted the full path name of the main configuration file must be the very
first argument to nanoweb.php
-o directive='value', --set-option='dir=val'
This command line option can be used to override configuration settings
from one of the configuration files.
Quotes or those ticks are neccessary, when your shell could otherwise
interpret some characters of the value as meta symbols (values containing
spaces should at least be enclosed in ticks or double quotes).
-a 'directive=value', --add-option=dir='val'
Use this to add a configuration setting where many may be given for a
Runs Nanoweb in daemon mode (as background server process), this is in the
"standard" mode (as opposite to inetd mode).
Supresses any messages that may be written to standard output.
Prints out the help screen with all available command line options.
Shows version information.
Nanoweb listens to environmental variables only when run in inetd mode, as
it needs to get the IP address and port of the requesting host via the helper
from the tcputils package in this case; but this is handled transparently by
(every daemon capable of being run from inetd utilizes such a wrapper).