Differences From Artifact [9b68473ad8]:
- File www/index.wiki — part of check-in [a2e7472d0f] at 2013-08-13 18:15:36 on branch trunk — Add support for SCGI via the --scgi command-line option to the "server" and "ui" and "http" commands. (user: drh size: 7754)
To Artifact [6f16fca989]:
- File www/index.wiki — part of check-in [b91754ab85] at 2013-08-13 23:05:27 on branch trunk — Further improvements to server documentation. No code changes. (user: drh size: 7734)
| ︙ | ︙ | |||
89 90 91 92 93 94 95 |
Fossil uses plain old HTTP (with
[./quickstart.wiki#proxy | proxy support])
for all network communications, meaning that it works fine from behind
restrictive firewalls. The protocol is
[./stats.wiki | bandwidth efficient] to the point that Fossil can be
used comfortably over a dial-up internet connection.
| | | | 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 |
Fossil uses plain old HTTP (with
[./quickstart.wiki#proxy | proxy support])
for all network communications, meaning that it works fine from behind
restrictive firewalls. The protocol is
[./stats.wiki | bandwidth efficient] to the point that Fossil can be
used comfortably over a dial-up internet connection.
6. <b>CGI/SCGI Enabled</b> -
No server is required to use fossil. But a
server does make collaboration easier. Fossil supports four different
yet simple [./server.wiki | server configurations].
The most popular is a 2-line CGI script. This is the approach
used by the [./selfhost.wiki | self-hosting fossil repositories].
7. <b>Robust & Reliable</b> -
Fossil stores content using an [./fileformat.wiki | enduring file format]
in an SQLite database so that transactions are
atomic even if interrupted by a power loss or system crash. Furthermore,
|
| ︙ | ︙ |