| 1 |
<h1>Document manager Administration manual</h1> |
| 2 |
|
| 3 |
<p>Here is a list of document that administrators might find useful when |
| 4 |
dealing with docman. They are ordered by importance, so be sure to read |
| 5 |
them. |
| 6 |
|
| 7 |
<h2>Reference reading</h2> |
| 8 |
<ol> |
| 9 |
<li><a href="install.html">Installation instructions</a> (<i>but, you already |
| 10 |
read that, right?</i>) |
| 11 |
<li><a href="faq.html">FAQ</a> and optionally |
| 12 |
<a href="upgrade.html">Upgrade from v1.x</a> |
| 13 |
<li><a href="new_directory_layout.html">New Directory Layout</a> and how that increase security |
| 14 |
<li><a href="performance.html">Performance tips</a> |
| 15 |
</ol> |
| 16 |
|
| 17 |
<h2>Errors</h2> |
| 18 |
|
| 19 |
<p>There are two types of errors in document manager: |
| 20 |
<ol> |
| 21 |
<li>errors which are result of user actions (<i>and they are reposted to users</i>) |
| 22 |
<li>errors which are result of configuration error (<i>which are by default reported to users, but they can be re-directed to error_log of Apache</i>) |
| 23 |
<br>You can re-direct administrative messages using |
| 24 |
<tt>$gblSeparateAdminMessages = 1</tt> in |
| 25 |
<tt>realm/http_virtual_host.conf</tt> |
| 26 |
<small>(See also explanation how to do that in |
| 27 |
<a href="install.html#gblSeparateAdminMessages">Installation instructions</a> |
| 28 |
)</small> |
| 29 |
</ol> |
| 30 |
|
| 31 |
<h2>Register Globals and PHP</h2> |
| 32 |
|
| 33 |
<p>Starting with version 2.0 docman doesn't need |
| 34 |
<tt>register_globals</tt> in <tt>php.ini</tt>. |
| 35 |
That means that docman knows which variables should be result of POST and |
| 36 |
what of GET which makes inserting bogus URL harder. |
| 37 |
</p> |
| 38 |
|
| 39 |
<h2>Unknown file types</h2> |
| 40 |
|
| 41 |
<p>By default, docman will report administrative error on |
| 42 |
unknown file types (like pipes, block and character files). |
| 43 |
You can change this behavior to ignoring those files by |
| 44 |
setting |
| 45 |
<tt>$gblIgnoreUnknownFileType = 0</tt> in |
| 46 |
<tt>realm/http_virtual_host.conf</tt> |
| 47 |
</p> |
| 48 |
|
| 49 |
<h2>Force download on view</h2> |
| 50 |
|
| 51 |
<p>If you set options |
| 52 |
<tt>$gblForceDownload= 1</tt> in |
| 53 |
<tt>realm/http_virtual_host.conf</tt> |
| 54 |
it will force download (and save to disk) if user wants to view file (just |
| 55 |
clicks on filename). Checkout will always force download. |
| 56 |
</p> |
| 57 |
|
| 58 |
<a name="path_realm"> |
| 59 |
<h2>Using script path as realm name</h2> |
| 60 |
|
| 61 |
<p>If you don't have ability to use http_virtual_host names for each docman |
| 62 |
installation, you can use path before docman.php as a identifier for a realm. |
| 63 |
To enable this, you will have to create directory named as same as virtual |
| 64 |
host, all directories wish exist before your <tt>docman.php</tt> and then |
| 65 |
<tt>conf</tt>, <tt>htusers</tt> and optionally <tt>trustee</tt> and |
| 66 |
<tt>info.inc</tt> files. |
| 67 |
<blockquote> |
| 68 |
e.g.: if your host is called <tt>dreamhouse.lan</tt> and |
| 69 |
you want to have repositories on URL |
| 70 |
<tt>http://dreamhouse.lan/project/</tt> and |
| 71 |
<tt>http://dreamhouse.lan/documentation/</tt> you will |
| 72 |
have to create following files: <small>(those marked with asterisk |
| 73 |
<sup>*</sup> are optional)</small> |
| 74 |
<br><tt>realm/dreamhouse.lan/project/conf</tt> |
| 75 |
<br><tt>realm/dreamhouse.lan/project/htusers</tt> |
| 76 |
<br><tt>realm/dreamhouse.lan/project/trustee</tt> <i>(optional)</i> |
| 77 |
<br><tt>realm/dreamhouse.lan/project/info.inc</tt> <i>(optional)</i> |
| 78 |
<br><tt>realm/dreamhouse.lan/documentation/conf</tt> |
| 79 |
<br><tt>realm/dreamhouse.lan/documentation/htusers</tt> |
| 80 |
<br><tt>realm/dreamhouse.lan/documentation/trustee</tt> <i>(optional)</i> |
| 81 |
<br><tt>realm/dreamhouse.lan/documentation/info.inc</tt> <i>(optional)</i> |
| 82 |
</blockquote> |
| 83 |
</p> |
| 84 |
|
| 85 |
<a name="path_realm_convert"> |
| 86 |
<h3>Conversion of files to realm with directories</h3> |
| 87 |
|
| 88 |
<p>If you followed <a href="install.html">installation instructions</a> |
| 89 |
and you want now to install docman to your host in directory <tt>projects</tt> |
| 90 |
which will be on disk at <tt>/home/httpd/htdocs/project/</tt> and |
| 91 |
served via URL <tt>http://my.host/project/</tt> |
| 92 |
you have to do few more steps: |
| 93 |
<pre> |
| 94 |
$ cd /home/httpd/docman2/realm/ |
| 95 |
$ mkdir my.host |
| 96 |
$ mkdir my.host/project |
| 97 |
$ mv http_virtual_host.htusers my.host/project/htusers |
| 98 |
$ mv http_virtual_host.conf my.host/project/conf |
| 99 |
</pre> |
| 100 |
That's it. You are ready to go... |
| 101 |
</p> |
| 102 |
|
| 103 |
<a name="info.inc"> |
| 104 |
<h2>Repository information files</h2> |
| 105 |
|
| 106 |
<p>There are special files, called <tt>info.inc</tt> files with informations |
| 107 |
which are local to that repository. Usually they are located in |
| 108 |
<tt>repository/.info.inc</tt> file. However, you can also use |
| 109 |
<tt>realm/http_host/script_path/info.inc</tt> file is you are |
| 110 |
using <a href="#path_realm">script path</a> as realm identifier. |
Parent Directory
| 
Revision Log