Fossil SCM

added some docs regarding read/write perms for CGI configurations, per ML thread.

stephan 2013-09-29 15:40 trunk
Commit 3892fcab71e6a45cd514453eba314f6459954562
1 file changed +16 -1
+16 -1
--- www/server.wiki
+++ www/server.wiki
@@ -129,16 +129,31 @@
129129
<blockquote><pre>
130130
#!/usr/bin/fossil
131131
repository: /home/fossil/repo.fossil
132132
</pre></blockquote>
133133
</p>
134
+
134135
<p>
135136
As always, adjust your paths appropriately.
136137
It may be necessary to set permissions properly, or to modify an ".htaccess"
137138
file or make other server-specific changes. Consult the documentation
138
-for your particular web server.
139
+for your particular web server. In particular, the following permissions are
140
+<em>normally</em> required (but, again, may be different for a particular
141
+configuration):
142
+
143
+<ul>
144
+<li>The Fossil binary must be readable/executable, and ALL directories leading up to it
145
+must be readable by the process which executes the CGI.</li>
146
+<li>ALL directories leading to the CGI script must also be readable and the CGI
147
+script itself must be executable for the user under which it will run (which often differs
148
+from the one running the web server - consult your site's documentation or administrator).</li>
149
+<li>The repository file AND the directory containing it must be writable by the same account
150
+which executes the Fossil binary (again, this might differ from the WWW user). The directory
151
+needs to be writable so that sqlite can write its journal files.</li>
152
+</ul>
139153
</p>
154
+
140155
<p>
141156
Once the script is set up correctly, and assuming your server is also set
142157
correctly, you should be able to access your repository with a URL like:
143158
<b>http://mydomain.org/cgi-bin/repo</b> (assuming the "repo" script is
144159
accessible under "cgi-bin", which would be a typical deployment on Apache
145160
--- www/server.wiki
+++ www/server.wiki
@@ -129,16 +129,31 @@
129 <blockquote><pre>
130 #!/usr/bin/fossil
131 repository: /home/fossil/repo.fossil
132 </pre></blockquote>
133 </p>
 
134 <p>
135 As always, adjust your paths appropriately.
136 It may be necessary to set permissions properly, or to modify an ".htaccess"
137 file or make other server-specific changes. Consult the documentation
138 for your particular web server.
 
 
 
 
 
 
 
 
 
 
 
 
 
139 </p>
 
140 <p>
141 Once the script is set up correctly, and assuming your server is also set
142 correctly, you should be able to access your repository with a URL like:
143 <b>http://mydomain.org/cgi-bin/repo</b> (assuming the "repo" script is
144 accessible under "cgi-bin", which would be a typical deployment on Apache
145
--- www/server.wiki
+++ www/server.wiki
@@ -129,16 +129,31 @@
129 <blockquote><pre>
130 #!/usr/bin/fossil
131 repository: /home/fossil/repo.fossil
132 </pre></blockquote>
133 </p>
134
135 <p>
136 As always, adjust your paths appropriately.
137 It may be necessary to set permissions properly, or to modify an ".htaccess"
138 file or make other server-specific changes. Consult the documentation
139 for your particular web server. In particular, the following permissions are
140 <em>normally</em> required (but, again, may be different for a particular
141 configuration):
142
143 <ul>
144 <li>The Fossil binary must be readable/executable, and ALL directories leading up to it
145 must be readable by the process which executes the CGI.</li>
146 <li>ALL directories leading to the CGI script must also be readable and the CGI
147 script itself must be executable for the user under which it will run (which often differs
148 from the one running the web server - consult your site's documentation or administrator).</li>
149 <li>The repository file AND the directory containing it must be writable by the same account
150 which executes the Fossil binary (again, this might differ from the WWW user). The directory
151 needs to be writable so that sqlite can write its journal files.</li>
152 </ul>
153 </p>
154
155 <p>
156 Once the script is set up correctly, and assuming your server is also set
157 correctly, you should be able to access your repository with a URL like:
158 <b>http://mydomain.org/cgi-bin/repo</b> (assuming the "repo" script is
159 accessible under "cgi-bin", which would be a typical deployment on Apache
160

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button