Fossil SCM
|
1
|
# Serving via althttpd |
|
2
|
|
|
3
|
[Althttpd][althttpd] |
|
4
|
is a light-weight web server that has been used to implement the SQLite and |
|
5
|
Fossil websites for well over a decade. Althttpd strives for simplicity, |
|
6
|
security, ease of configuration, and low resource usage. |
|
7
|
|
|
8
|
To set up a Fossil server as CGI on a host running the althttpd web |
|
9
|
server, follow these steps. |
|
10
|
<ol> |
|
11
|
<li>Get the althttpd webserver running on the host. This is easily |
|
12
|
done by following the [althttpd documentation][althttpd]. |
|
13
|
|
|
14
|
<li>Create a CGI script for your Fossil repository. The script will |
|
15
|
be typically be two lines of code that look something like this: |
|
16
|
|
|
17
|
~~~ |
|
18
|
#!/usr/bin/fossil |
|
19
|
repository: /home/yourlogin/fossils/project.fossil |
|
20
|
~~~ |
|
21
|
|
|
22
|
Modify the filenames to conform to your system, of course. The |
|
23
|
CGI script accepts [other options][cgi] besides the |
|
24
|
repository:" line. You can add in other options as you desire, |
|
25
|
but the single "repository:" line is normally all that is needed |
|
26
|
to get started. |
|
27
|
|
|
28
|
<li>Make the CGI script executable. |
|
29
|
|
|
30
|
<li>Verify that the fossil repository file and the directory that contains |
|
31
|
the repository are both writable by whatever user the web server is |
|
32
|
running and. |
|
33
|
</ol> |
|
34
|
|
|
35
|
And you are done. Visit the URL that corresponds to the CGI script |
|
36
|
you created to start using your Fossil server. |
|
37
|
|
|
38
|
*[Return to the top-level Fossil server article.](../)* |
|
39
|
|
|
40
|
|
|
41
|
[althttpd]: https://sqlite.org/althttpd/ |
|
42
|
[cgi]: ../../cgi.wiki |
|
43
|
|