Help: server

The "server" command:

Usage: fossil server ?OPTIONS? ?REPOSITORY?
or: fossil ui ?OPTIONS? ?REPOSITORY?

Open a socket and begin listening and responding to HTTP requests on TCP port 8080, or on any other TCP port defined by the -P or --port option. The optional argument is the name of the repository. The repository argument may be omitted if the working directory is within an open checkout.

The "ui" command automatically starts a web browser after initializing the web server. The "ui" command also binds to and so will only process HTTP traffic from the local machine.

The REPOSITORY can be a directory (aka folder) that contains one or more repositories with names ending in ".fossil". In this case, a prefix of the URL pathname is used to search the directory for an appropriate repository. To thwart mischief, the pathname in the URL must contain only alphanumerics, "_", "/", "-", and ".", and no "-" may occur after "/", and every "." must be surrounded on both sides by alphanumerics. Any pathname that does not satisfy these constraints results in a 404 error. Files in REPOSITORY that match the comma-separated list of glob patterns given by --files and that have known suffixes such as ".txt" or ".html" or ".jpeg" and do not match the pattern "*.fossil*" will be served as static content. With the "ui" command, the REPOSITORY can only be a directory if the --notfound option is also present.

For the special case REPOSITORY name of "/", the list global configuration database is consulted for a list of all known repositories. The --repolist option is implied by this special case. See also the "fossil all ui" command.

By default, the "ui" command provides full administrative access without having to log in. This can be disabled by turning off the "localauth" setting. Automatic login for the "server" command is available if the --localauth option is present and the "localauth" setting is off and the connection is from localhost. The "ui" command also enables --repolist by default.


--baseurl URL
Use URL as the base (useful for reverse proxies)
--ckout-alias NAME
Treat URIs of the form /doc/NAME/... as if they were /doc/ckout/...
Create a new REPOSITORY if it does not already exist
--extroot DIR
Document root for the /ext extension mechanism
--files GLOBLIST
Comma-separated list of glob patterns for static files
enable automatic login for requests from localhost
listen on only (always true for "ui")
Indicates that the input is coming through a reverse proxy that has already translated HTTPS into HTTP.
--jsmode MODE
Determine how JavaScript is delivered with pages. Mode can be one of:
All JavaScript is inserted inline at the end of the HTML file.
Separate HTTP requests are made for each JavaScript file.
One single separate HTTP fetches all JavaScript concatenated together.
Depending on the needs of any given page, inline and bundled modes might result in a single amalgamated script or several, but both approaches result in fewer HTTP requests than the separate mode.
--max-latency N
Do not let any single HTTP request run for more than N seconds (only works on unix)
Do not compress HTTP replies
Drop root privileges but do not enter the chroot jail
signal that no SSL connections are available (Always set by default for the "ui" command)
--notfound URL
--page PAGE
Start "ui" on PAGE. ex: --page "timeline?y=ci"
-P|--port TCPPORT
listen to request on port TCPPORT
trace TH1 execution (for debugging purposes)
If REPOSITORY is dir, URL "/" lists repos.
Accept SCGI rather than HTTP
--skin LABEL
Use override skin LABEL
--mainmenu FILE
Override the mainmenu config setting with the contents of the given file.
Use saved encryption key from parent process. This is only necessary when using SEE on Windows.

See also: cgi, http, winsrv