1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "../../../dtd/docbookx.dtd" [
3 <!ENTITY % authors SYSTEM "../entities/authors.ent">
6 <article lang="en-US" id="installation_guide">
8 <title>GForge Installation Guide</title>
17 <title>Hardware Requirements</title>
19 Hardware requirements are dependent on the number of users that will use the system and how active those users are.
22 For instance, an installation of GForge hosts over 450 users and over 140 projects on a single CPU Pentium 2.4GHz machine with 512 MB of RAM.
25 You can find additionnal information about hardware used by several installations of GForge in the <ulink url="http://gforge.org/docman/view.php/1/52/gforge-sites.html">GForge sites list maintained by Tom Copeland</ulink>.
29 <title>Software Requirements</title>
31 GForge should work correctly on any system configured like this:
34 <listitem><para>Linux Operating System</para></listitem>
35 <listitem><para><ulink url="http://www.postgresql.org/">PostgreSQL</ulink> 7.3 or later</para></listitem>
36 <listitem><para><ulink url="http://www.apache.org/">Apache</ulink> 1.3.22 or later</para></listitem>
37 <listitem><para><ulink url="http://www.openssl.org/">openssl</ulink> 0.9.4 or later</para></listitem>
38 <listitem><para><ulink url="http://www.openssl.org/">mod_ssl</ulink> 2.4.10 or later (included in Apache 2.0 and later)</para></listitem>
39 <listitem><para><ulink url="http://www.php.net/">PHP</ulink> 4.0.4 or later (note that you'll need to have PHP built with the command line interface support, which only comes standard with PHP 4.3 or later)</para></listitem>
40 <listitem><para>php-pgsql (enable it with <literal>--with-pgsql</literal> when building PHP, or install it as package)</para></listitem>
41 <listitem><para>php-mbstring (enable it with <literal>--with-mbstring</literal> when building PHP, or install it as package)</para></listitem>
47 <listitem><para><ulink url="http://turck-mmcache.sourceforge.net">Turck MMCache</ulink> or <ulink url="http://www.php-accelerator.co.uk/">PHP Accelerator</ulink> or any other PHP accelerator (highly recommended)</para></listitem>
48 <listitem><para><ulink url="http://www.gnu.org/software/mailman/">GNU Mailman</ulink> and <ulink url="http://www.python.org/">Python</ulink> (Mailing list support)</para></listitem>
49 <listitem><para><ulink url="http://jabberd.jabberstudio.org/">Jabberd</ulink> (Jabber support)</para></listitem>
50 <listitem><para><ulink url="http://www.aditus.nu/jpgraph/">JPGraph</ulink> (Gantt Charting and Graphing Support)</para></listitem>
51 <listitem><para><ulink url="http://www.perl.org/">Perl</ulink>, <ulink url="http://dbi.perl.org/">DBI module</ulink> and associated <literal>DBD::Pg</literal>.</para></listitem>
54 Successful installations and operations have been done using the following systems:
58 <para>Debian GNU/Linux 3.1 (Sarge)</para>
61 <para>RedHat Enterprise Linux 3 with bundled packages except for a compiled GNU Mailman</para>
64 <para>RedHat Linux 9 with bundled packages except for a compiled GNU Mailman</para>
69 <title>Installation</title>
71 <title>Overview</title>
73 <para>This installation guide is for GForge 4.5.0.1.</para>
75 <para>GForge has a lot of different pieces touching a lot of different components in the system. Cronjobs are required to maintain the system, touching lots of files on a daily and hourly basis, including <filename>/etc/*</filename> system files.</para>
76 <para>The plugins that now manage the CVS and SVN functionality have made installation slightly harder because even more files have to be moved into place during installation.</para>
77 <para>The manual installation of GForge is documented below. Be sure to follow each step carefully, check the forums for frequently asked questions, and ask your Apache, Mailman, and PostgreSQL installation questions in the corresponding mailing lists rather than on the GForge forums where little help is available.</para>
80 <title>Installing on Debian</title>
82 You can simply add lines found at <ulink url="http://people.debian.org/~bayle/"/> or <ulink url="http://roland.mas.free.fr/"/> to <filename>/etc/apt/sources.list</filename> and type <command>apt-get install gforge</command> to install a working GForge system, thanks to Christian Bayle and Roland Mas.
85 Note that GForge is now part of official Debian, and so you can find it in all debian mirrors all other the planet. Package versions of GForge may lag behind upstream versions. From scratch install snapshot are also available for a guided installation.
89 <title>Installing on RPM-based systems</title>
90 <para>Guillaume Smet makes <ulink url="http://people.openwide.fr/~gsmet/gforge/rpm/">RPM packages for installing GForge</ulink>. If you are using Fedora Core or Red Hat Enterprise Linux, you may want to try them.</para>
93 <title>Installing GForge</title>
95 <title>Directory Layout</title>
96 <para>Instructions below assume that gforge is unpacked into <filename class="directory"><replaceable>/var/www/gforge</replaceable></filename>. There are some other directories where GForge stores files. In this installation guide, they are put in <filename class="directory">/var/www</filename> too.</para>
98 <para>If you want to be <ulink url="http://www.pathname.com/fhs/">FHS</ulink>-compliant, GForge should be unpacked into <filename class="directory">/usr/local/share/gforge</filename>, and directories for storing files should be in <filename class="directory">/var/lib/gforge</filename> or <filename class="directory">/var/local/gforge</filename>. You may use symbolic links to physically place files in FHS-compliant places and still use directory paths that are presented in this manual.</para>
102 <title>Unpacking</title>
103 <para>To install GForge, follow these steps (as root):</para>
105 # <userinput>bzip2 -dc gforge-4.5.tar.bz2 | tar xvf -</userinput>
106 # <userinput>mv gforge-4.5 <replaceable>/var/www/gforge</replaceable></userinput>
110 <title>GForge Config File</title>
111 <para>In the GForge distribution, you will find <filename>etc/local.inc.example</filename>. Copy it to <filename>/etc/gforge/local.inc</filename> and edit all of the settings. In later sections, there is more information about specific configuration settings. Usually, you will want to make it readable only by webserver user (see <xref linkend="web-server"/> for <replaceable>apache-user</replaceable> and <replaceable>apache-group</replaceable>):</para>
113 # <userinput>mkdir /etc/gforge</userinput>
114 # <userinput>chown root: /etc/gforge</userinput>
115 # <userinput>chmod 755 /etc/gforge</userinput>
116 # <userinput>cp <replaceable>/var/www/gforge</replaceable>/etc/local.inc.example /etc/gforge/local.inc</userinput>
117 # <userinput>chown <replaceable>apache-user</replaceable>:<replaceable>apache-group</replaceable> /etc/gforge/local.inc</userinput>
118 # <userinput>chmod 600 /etc/gforge/local.inc</userinput>
122 <title>Configuring GForge</title>
123 <para>Open <filename>/etc/gforge/local.inc</filename>, configuring the following basic parameters:</para>
126 <para>Database configuration:</para>
128 $sys_dbhost="localhost"
131 $sys_dbpasswd="gforge"
132 $sys_server="postgres"
136 <para>Change the following basic variables::</para>
138 $sys_urlroot="<replaceable>/var/www/gforge</replaceable>/www/";
139 $sys_themeroot="<replaceable>/var/www/gforge</replaceable>/www/themes/";
140 $sys_plugins_path="<replaceable>/var/www/gforge</replaceable>/plugins/";
144 <para>The directives <varname>$sys_default_domain</varname> and <varname>$sys_fallback_domain</varname> should contain the domain of your server, e.g. <literal>gforge.org</literal>.</para>
150 <title>Configuring the Database (PostgreSQL)</title>
152 <title>Initialization of PostgreSQL</title>
153 <para>In some distributions, PostgreSQL database cluster is not initialised. Consult distribution documentation for more information. If database cluster is not created, you can do so by running:</para>
155 # <userinput>su - postgres</userinput>
156 $ <userinput>initdb</userinput>
159 <para>This will wipe out any existing PostgreSQL databases!</para>
164 <title>PostgreSQL Authentication Configuration</title>
165 <para>The <literal>postgres</literal> PostgreSQL user is used only during installation. Usually, it can connect via UNIX socket without password when invoked by <literal>postgresql</literal> system account. Check by running this:</para>
167 # <userinput>su - postgres</userinput>
168 $ <userinput>psql template1</userinput>
170 <para>If connection fails, add the following line to <filename>pg_hba.conf</filename>:</para>
172 local all postgres ident sameuser
174 <para>GForge uses <literal>gforge</literal> PostgreSQL user to connect to <literal>gforge</literal> database by using password. (You can change that name by editing <filename>local.inc</filename>.) In order this to work, assure that you have the following line in your <filename>pg_hba.conf</filename>:</para>
176 host gforge gforge 127.0.0.1 255.255.255.255 md5
178 <para>This line assumes that GForge will always use local PostgreSQL database (<literal>localhost</literal>). If this is not the case, consult PostgreSQL manual for ways to allow connection.</para>
179 <para>The following option should be set in <filename>postgresql.conf</filename> because connection to <literal>localhost</literal> uses TCP/IP:</para>
183 <para>After all these changes to PostgreSQL configuration files are made, PostgreSQL should be restarted. This depends on the distribution. In Debian, it's like this:</para>
185 # <userinput>/etc/init.d/postgresql restart</userinput>
189 <title>Importing Database</title>
190 <para>Create GForge database user:</para>
192 # <userinput>su - postgres</userinput>
193 $ <userinput>psql template1</userinput>
194 template1=# <userinput>CREATE USER gforge NOCREATEUSER NOCREATEDB</userinput>
195 template1-# <userinput>PASSWORD '<replaceable>gforge-password</replaceable>';</userinput>
197 <para>Create GForge database:</para>
199 template1=# <userinput>CREATE DATABASE gforge OWNER gforge ENCODING 'UNICODE';</userinput>
201 <para>Add PL/pgSQL support using the commands:</para>
203 # <userinput>su - postgres</userinput>
204 $ <userinput>createlang plpgsql gforge</userinput>
206 <para>Finally, install the database:</para>
208 $ <userinput>cd <replaceable>/var/www/gforge</replaceable>/db</userinput>
209 $ <userinput>psql -a -U gforge -W -h localhost -f gforge.sql gforge &> /tmp/gforge.sql.log</userinput>
212 <para>You may experience the following errors. They are harmless and you can safely ignore them:</para>
214 ERROR: permission denied for language c
215 ERROR: must be superuser to create procedural language
216 ERROR: permission denied for schema public
220 <title>Full Text Indexing</title>
221 <para>If you want to enable full text indexing, follow these steps:</para>
224 <para>Find <filename>tsearch2.sql</filename> in your distribution of PostgreSQL and run it:</para>
226 # <userinput>su - postgres</userinput>
227 $ <userinput>psql -f <replaceable>/path/to/</replaceable>tsearch2.sql gforge</userinput>
229 <para>Since <literal>gforge</literal> PostgreSQL user is not superuser, access to some Tsearch2 tables should be additionally granted:</para>
231 # <userinput>su - postgres</userinput>
232 $ <userinput>psql gforge</userinput>
233 gforge=# <userinput>GRANT SELECT ON pg_ts_dict TO gforge;</userinput>
234 gforge=# <userinput>GRANT SELECT ON pg_ts_parser TO gforge;</userinput>
235 gforge=# <userinput>GRANT SELECT ON pg_ts_cfg TO gforge;</userinput>
236 gforge=# <userinput>GRANT SELECT ON pg_ts_cfgmap TO gforge;</userinput>
240 <para>Import data definitions:</para>
242 $ <userinput>cd <replaceable>/var/www/gforge</replaceable>/db</userinput>
243 $ <userinput>psql -U gforge -W -h localhost -f FTI.sql gforge</userinput>
244 $ <userinput>psql -U gforge -W -h localhost -f FTI-20050315.sql gforge</userinput>
245 $ <userinput>psql -U gforge -W -h localhost -f FTI-20050401.sql gforge</userinput>
246 $ <userinput>psql -U gforge -W -h localhost -f FTI-20050530.sql gforge</userinput>
250 <para>Enable Full Text Indexing by setting <varname>$sys_use_fti</varname> in GForge Configuration File <filename>local.inc</filename>.</para>
257 <title>Configuring DNS Server (BIND)</title>
258 <para>GForge needs its own domain. In example GForge configuration file, it's <literal>gforge.<replaceable>company.com</replaceable></literal>. You should search for <replaceable>company.com</replaceable> in example GForge configuration file and replace it with your domain name.</para>
259 <para>Here some example configuration files for BIND are presented that can help you if you are not familiar with BIND but it's not meant to be complete. Don't ask BIND-related questions in GForge forums – consult documentation that come with your distribution and search in Internet. Distributions put files in different places and so there are no file locations here. The example configuration below is only quick start example and doesn't include reverse mapping.</para>
260 <para>New subdomain in <literal>gforge.<replaceable>company.com</replaceable></literal> should be created. In <replaceable>company.com</replaceable> zone file, it may look like that:</para>
262 gforge IN NS ns.gforge.<replaceable>company.com</replaceable>.
263 ns.gforge IN A <replaceable>1.2.3.4</replaceable>
266 <para>Do not add the latter resource record (<literal>ns.gforge</literal>) if this DNS server serves both <literal><replaceable>company.com</replaceable></literal> and <literal>gforge.<replaceable>company.com</replaceable></literal> zones.</para>
268 <para>New zone file for <literal>gforge.<replaceable>company.com</replaceable></literal> may look like this:</para>
271 @ IN SOA gforge.<replaceable>company.com</replaceable>. hostmaster.gforge.<replaceable>company.com</replaceable>. (
276 3600 ) ; Negative Cache TTL
278 @ IN NS ns.gforge.<replaceable>company.com</replaceable>.
279 @ IN A <replaceable>1.2.3.4</replaceable>
280 ns IN A <replaceable>1.2.3.4</replaceable>
282 download IN A <replaceable>1.2.3.4</replaceable>
283 shell IN A <replaceable>1.2.3.4</replaceable>
284 users IN A <replaceable>1.2.3.4</replaceable>
285 lists IN A <replaceable>1.2.3.4</replaceable>
286 cvs IN A <replaceable>1.2.3.4</replaceable>
287 svn IN A <replaceable>1.2.3.4</replaceable>
288 scm IN A <replaceable>1.2.3.4</replaceable>
289 ldap IN A <replaceable>1.2.3.4</replaceable>
290 jabber IN A <replaceable>1.2.3.4</replaceable>
292 <para>The new zone must be added in main BIND configuration file:</para>
294 zone "gforge.<replaceable>company.com</replaceable>" {
296 file "<replaceable>/dist-specific/path/to/zone-file</replaceable>";
299 <para>Of course, changes will take effect after reloading BIND.</para>
302 <title>Configuring PHP</title>
303 <para>PHP is used in two ways:</para>
306 <para><emphasis>Serving Web pages</emphasis>. In this case, PHP is usually used as module and its configuration is in virtual host configuration, as shown later in document. If you prefer to configure <filename>php.ini</filename>, the following directives are required by GForge:</para>
308 register_globals = On
309 magic_quotes_gpc = On
311 include_path=".:<replaceable>/var/www/gforge</replaceable>:<replaceable>/var/www/gforge</replaceable>/www/include:/etc/gforge"
315 <para><emphasis>Cron jobs and some scripts</emphasis> require PHP Command-Line Interface (CLI). Scripts are usually invoked with command like this:</para>
317 $ <userinput>php4 -f cronjobs/mail/mailing_lists_create.php</userinput>
320 <para>The <literal>-f</literal> is optional when using PHP CLI but it's required when PHP CGI executable is used.</para>
322 <para>You must set <varname>include_path</varname> in PHP CLI <filename>php.ini</filename>, like already shown above. To find where <filename>php.ini</filename> is located, use the following command:</para>
324 $ <userinput>php4 -i | fgrep php.ini</userinput>
329 <section id="web-server">
330 <title>Configuring the Web Server (Apache)</title>
331 <para>First, you should decide where to put GForge configuration of Apache. It's best if own configuration file that is included by main Apache configuration is used. Consult documentation of your distribution on recommended ways for doing this.</para>
332 <para>You may use <filename>etc/gforge-httpd.conf.example</filename> as template for your configuration. The rest of the section is guide to making GForge virtual host configuration for Apache from scratch. All is inside the following template:</para>
334 NameVirtualHost <replaceable>1.2.3.4</replaceable>
335 <VirtualHost <replaceable>1.2.3.4</replaceable>>
337 <replaceable># Put the rest of the directives here.</replaceable>
342 <para>Configuring for SSL is not discussed in this guide.</para>
346 <para>Set basic virtual host settings:</para>
348 ServerName gforge.<replaceable>company.com</replaceable>
349 ServerAdmin webmaster@gforge.<replaceable>company.com</replaceable>
353 <para>Define log files:</para>
355 CustomLog "<replaceable>/var/log/gforge</replaceable>/gforge/access.log" combined
356 ErrorLog "<replaceable>/var/log/gforge</replaceable>/gforge/error.log"
358 <para>Usual practice is to use <command>logrotate</command> on these files. Alternative is to pipe logs to <command>cronolog</command> which will automatically make directory with <filename>access.log</filename> and <filename>error.log</filename> for each day:</para>
360 CustomLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/gforge/%Y/%m/%d/access.log" combined
361 ErrorLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/gforge/%Y/%m/%d/error.log"
364 <para>In FHS-compliant install, you may want to use <filename class="directory">/var/local/gforge/log</filename> instead of <filename class="directory">/var/log/gforge</filename>. In any cases, the relevant directories should be created with appropriate permissions.</para>
368 <para>Set up document root:</para>
370 DocumentRoot "<replaceable>/var/www/gforge</replaceable>/www"
371 <Directory "<replaceable>/var/www/gforge</replaceable>/www">
372 Options FollowSymLinks
376 ErrorDocument 404 /404.php
381 <para>Configuring PHP for Apache</para>
382 <para>Ensure that PHP module is loaded. You may need to consult your distribution manual. Typical lines that load and configure PHP module are like this:</para>
384 LoadModule php_module modules/libphp.so
387 AddType application/x-httpd-php .php
389 <para>Insert the following instructions after the <literal>DocumentRoot</literal> directive:</para>
391 <Location /projects>
392 ForceType application/x-httpd-php
394 <Location /users>
395 ForceType application/x-httpd-php
399 <para>If you use Apache 2, you may need to use a different configuration. Usually, this is not neede.</para>
400 <para>Change the existing <literal>Files</literal> directive to:</para>
406 LimitRequestBody 2097152
409 <para>The <literal>LimitRequestBody</literal> directive allows you to limit the maximum number of bytes of a request (including uploads). The default is 524288 (512Kb). This means that you cannot upload files with a size greater than 512Kb. With this directive, we set it to 2MB. If you wish to set this value higher than 2MB, you must also edit the <literal>upload_max_filesize</literal> directive in PHP configuration file.</para>
410 <para>Add the following lines:</para>
412 <Files projects>
427 <para>Set up PHP module:</para>
429 php_flag register_globals On
430 php_flag gpc_magic_quotes On
431 php_flag files_uploads On
432 php_value include_path ".:/etc/gforge:<replaceable>/var/www/gforge</replaceable>:<replaceable>/var/www/gforge</replaceable>/www/include"
433 php_value default_charset "UTF-8"
437 <para>Set up directory index script name:</para>
439 DirectoryIndex index.php
443 <para>Of couse, all changes will take effect only after reloading or restarting Apache.</para>
445 <title>Project webs</title>
446 <para>Each project can have its own virtual host <literal><replaceable>projectname</replaceable>.projects.gforge.<replaceable>company.com</replaceable></literal>. Location of project files is configured with <varname>$groupdir_prefix</varname> variable in GForge configuration file. Each project has directory with project's name and contains <filename class="directory">htdocs</filename> subdirectory where Web files are placed. Project directories are created by <filename>cronjobs/cvs-cron/usergroup.php</filename>.</para>
448 <title>DNS Server Configuration (BIND)</title>
449 <para>Project virtual hosts require new DNS zone. Making this new zone is similar to making DNS zone for GForge itself.</para>
452 <para>Declare new zone in <literal>gforge.<replaceable>company.com</replaceable></literal> zone:</para>
454 projects IN NS ns.projects.gforge.<replaceable>company.com</replaceable>
456 <para>If DNS server <emphasis>doesn't</emphasis> serve the new <literal>projects.gforge.<replaceable>company.com</replaceable></literal> zone, add the following line too:</para>
458 ns.projects IN A <replaceable>1.2.3.4</replaceable>
460 <para>Don't forget to change serial number of <literal>gforge.<replaceable>company.com</replaceable></literal> zone!</para>
463 <para>Create new zone file with following content:</para>
466 @ IN SOA projects.gforge.<replaceable>company.com</replaceable>. hostmaster.gforge.<replaceable>company.com</replaceable>. (
471 3600 ) ; Negative Cache TTL
473 @ IN NS ns.projects.gforge.<replaceable>company.com</replaceable>.
474 @ IN A <replaceable>1.2.3.4</replaceable>
475 ns IN A <replaceable>1.2.3.4</replaceable>
477 * IN A <replaceable>1.2.3.4</replaceable>
481 <para>The new zone must be added in main BIND configuration file:</para>
483 zone "projects.gforge.<replaceable>company.com</replaceable>" {
485 file "<replaceable>/dist-specific/path/to/zone-file</replaceable>";
490 <para>Reload BIND and test if all works:</para>
492 $ <userinput>host test.projects.gforge.<replaceable>company.com</replaceable></userinput>
498 <title>Web Server Configuration (Apache)</title>
499 <para>Module <literal>vhost_alias</literal> should be enabled and the following directives should be added to <filename>httpd.conf</filename> (<filename class="directory"><replaceable>/var/www/homedirs</replaceable>/groups</filename> is what you have chosen in <varname>$groupdir_prefix</varname>):</para>
501 <para>If you want to be FHS-compliant, you may use <filename>/var/local/gforge/log</filename> and <filename>/var/local/gforge/homedirs</filename>. </para>
505 # WARNING - security is degraded by having this
506 # on the same machine as the primary GForge
508 NameVirtualHost <replaceable>1.2.3.4</replaceable>
509 <VirtualHost <replaceable>1.2.3.4</replaceable>>
510 ServerName projects.gforge.<replaceable>company.com</replaceable>
511 ServerAlias *.gforge.<replaceable>company.com</replaceable>
514 # You may want to add these files to logrotate, or just use cronolog as shown below
515 CustomLog "<replaceable>/var/log/gforge</replaceable>/projects/access.log" combined
516 ErrorLog "<replaceable>/var/log/gforge</replaceable>/projects/error.log"
518 # CustomLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/projects/%Y/%m/%d/access.log" combined
519 # ErrorLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/projects/%Y/%m/%d/error.log"
521 DocumentRoot <replaceable>/var/www/homedirs</replaceable>/groups
522 VirtualDocumentRoot <replaceable>/var/www/homedirs</replaceable>/groups/%1/htdocs
523 <Directory <replaceable>/var/www/homedirs</replaceable>/groups>
526 # WARNING - turning on php will allow any user
527 # to upload a php file to your server, and include
528 # the gforge local.inc file and get your password to
529 # connect to the database and have total control.
536 DirectoryIndex index.html index.htm
540 <para><filename>cronjobs/cvs-cron/usergroup.php</filename> creates <filename>index.php</filename> file in Web directory (<filename class="directory">htdocs</filename>) of project but the above configuration disables PHP.</para>
546 <title>Configuring Mail Transport Agent (Any)</title>
547 <para>Add the following line to <filename>/etc/aliases</filename> and run <command>newaliases</command>:</para>
551 <para>Make sure that the following domain names are accepted as local destinations by mail transport agent:</para>
554 <para><literal>gforge.<replaceable>company.com</replaceable></literal></para>
557 <para><literal>lists.gforge.<replaceable>company.com</replaceable></literal></para>
560 <para><literal>users.gforge.<replaceable>company.com</replaceable></literal></para>
563 <para>You may want to consider adding <literal>MX</literal> (mail exchanger) resource records for the above domain names. This is meaningful only if you want fallback mail routes or if firewall doesn't allow incoming port 25 for the server.</para>
565 <title>Mail gateways to forum and tracker</title>
566 <para>When forum or tracker is monitored, replying to monitor mails are processed by mail gateways. These gateways use GForge configuration file <filename>/etc/gforge/local.inc</filename> so that they can access database but the problem is that they run with different user than that of Apache. So if you want to use these gateways, you'll have to change access mode of <filename>local.inc</filename>.</para>
570 <title>File Release System (FRS)</title>
571 <para>Create a directory (e.g. <filename class="directory"><replaceable>/var/lib/gforge</replaceable>/download</filename>) and make it owned by the webserver user. This directory will be referenced in the GForge Config File <filename>/etc/gforge/local.inc</filename> as <varname>$sys_upload_dir</varname>.</para>
573 # <userinput>mkdir <replaceable>/var/lib/gforge</replaceable>/download</userinput>
574 # <userinput>chown -R <replaceable>apache-user</replaceable> <replaceable>/var/lib/gforge</replaceable>/download</userinput>
577 <para>For FHS-compliance, use <filename class="directory">/var/local/gforge/download</filename>.</para>
581 <title>Configuring GNU Mailman</title>
582 <para>GNU Mailman is used to help manage the GForge mailing lists. Mailman is frequently installed in <filename class="directory">/usr/lib/mailman</filename> but sometimes it can be found in <filename class="directory">/var/mailman</filename>. You should change GForge configuration variable <varname>$sys_path_to_mailman</varname> to that Mailman directory.</para>
583 <para>Cronjobs for Mailman are located in <filename>cronjobs/mail/*</filename>. <filename>cronjobs/mail/mailing_lists_create.php</filename> is used obviously to create new mailing lists.</para>
584 <para>For all problems with Mailman installation and use, contact the Mailman mailing lists for help.</para>
585 <para>To install it:</para>
588 <para>Install a GNU Mailman package or compile it</para>
591 <para>Don't integrate Mailman with Postfix (or other MTA) by delegating it generation of alias-style file. GForge generates such file. But you'll need to put mail aliases in <filename>/etc/aliases</filename> for the required standard <literal>mailman</literal> mailing list. Create it with:</para>
593 # <replaceable>/usr/lib/mailman/bin</replaceable>/newlist mailman
597 <para>Configure <filename>mm_cfg.py</filename>:</para>
600 <para><varname>DEFAULT_HOST_NAME</varname> and <varname>DEFAULT_URL</varname> should point to <literal>lists.gforge.<replaceable>company.com</replaceable></literal>. These variable names may vary depending on Mailman distribution.</para>
603 <para>Don't use ugly <literal>cgi-bin</literal> as part of URLs.</para>
608 <para><command>su</command> to <literal>root</literal> and set the Mailman password by using the <command>mmsitepass</command> command</para>
611 <para>Create directory <filename class="directory"><replaceable>/var/www/mailman</replaceable>/</filename>. It will be document root for <literal>lists.gforge.<replaceable>company.com</replaceable>.</literal></para>
614 <para>In Web server configuraton, create virtual host for Mailman, adjusting <literal>ScriptAlias</literal> and <literal>Alias</literal> directives:</para>
616 <VirtualHost <replaceable>1.2.3.4</replaceable>>
617 ServerName lists.gforge.<replaceable>company.com</replaceable>
618 ServerAdmin mailman@lists.gforge.<replaceable>company.com</replaceable>
620 # You may want to add these files to logrotate, or just use cronolog as shown below
621 CustomLog "<replaceable>/var/log/gforge</replaceable>/lists/access.log" combined
622 ErrorLog "<replaceable>/var/log/gforge</replaceable>/lists/error.log"
624 # CustomLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/lists/%Y/%m/%d/access.log" combined
625 # ErrorLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/lists/%Y/%m/%d/error.log"
627 DocumentRoot <replaceable>/var/www/mailman</replaceable>
628 DirectoryIndex index.html
629 ScriptAlias /mailman/ <replaceable>/usr/lib/cgi-bin/mailman/</replaceable>
630 Alias /pipermail/ <replaceable>/var/lib</replaceable>/mailman/archives/public/
631 Alias /doc/ <replaceable>usr/share/images/mailman/</replaceable>
635 <para>Check that <literal>ScriptAlias</literal> and <literal>Alias</literal> directories are correct. The example values are for Debian 3.1 (Sarge).</para>
640 <title>Mailing list for commits</title>
641 <para>When repositories are created, mailing list <literal><replaceable>project</replaceable>-commits@lists.gforge.<replaceable>company.com</replaceable></literal> is created too. Note that project administrators should manually set Privacy Options... / Sender filters / accept_these_nonmembers to something like <literal>^.*@<replaceable>servername\.company\.com</replaceable></literal> where <replaceable>servername.company.com</replaceable> is name of the host where Mailman is installed (<literal>lists.gforge.<replaceable>company.com</replaceable></literal>).</para>
645 <title>Source Code Management (SCM)</title>
646 <para>CVS and Subversion (SVN) are popular SCM systems that may be installed as plugins, as shown later. You'll have to make their needed directories:</para>
648 # <userinput>mkdir <replaceable>/var/www</replaceable>/scmtarballs</userinput>
649 # <userinput>mkdir <replaceable>/var/www</replaceable>/scmsnapshots</userinput>
651 <para>These directories correspond to GForge configuration variables <varname>$sys_scm_tarballs_path</varname> and <varname>$sys_scm_snapshots_path</varname>.</para>
653 <para>For FHS-compliance, use <filename class="directory">/var/local/gforge/scmtarballs</filename> and <filename class="directory">/var/local/gforge/scmsnapshots</filename>.</para>
657 <title>Cron Jobs</title>
659 Cron jobs are in the <filename class="directory">cronjobs/</filename> directory and the <filename>crontab.in</filename> file contains a sample crontab. This gives you the basic cronjobs for updating certain statistics and data on the site.
662 <filename class="directory">cronjobs/cvs-cron/</filename> contains scripts useful for creating blank cvs trees and managing the <filename>/etc/groups</filename>, <filename>/etc/passwd</filename> and <filename>/etc/shadow</filename> files. See <filename>cronjobs/README.root</filename> and CVS plugins section for more info.
665 <filename class="directory">cronjobs/mail/</filename> contains files useful for the creation of new mailing lists in mailman and creating the <filename>/etc/aliases</filename> file.
667 <para>Prepare for <filename>cronjobs/cvs-cron/usergroup.php</filename> and <filename>cronjobs/mail/mailaliases.php</filename>.</para>
669 # <userinput>adduser anonymous</userinput>
670 # <userinput>cp /etc/aliases /etc/aliases.org</userinput>
671 # <userinput>cp /etc/shadow /etc/shadow.org</userinput>
672 # <userinput>cp /etc/passwd /etc/passwd.org</userinput>
673 # <userinput>cp /etc/group /etc/group.org</userinput>
676 <para>There are two other ways to authenticate GForge users: LDAP and NSS with PostgreSQL backend. They are not discussed in this guide.</para>
679 <para>The <filename>cronjobs/cvs-cron/usergroup.php</filename> cron script will meddle with your <filename>/etc/passwd</filename>, <filename>/etc/group</filename>, and <filename>/etc/shadow</filename> files. By default, this cron will save these files with a <literal>.new</literal> extension. You will have to edit the cron script to remove the <literal>.new</literal> extension, but you must make sure that it is properly generating your files or your server could be unusable.</para>
683 The following command will blow away any existing root crontab:
687 # crontab cronjobs/crontab.in
689 <para>Now edit the paths to the cron scripts by setting the value of <varname>GFORGE</varname> and <varname>PHP</varname> variables:</para>
693 <para>Uncomment entries for <filename>cronjobs/cvs-cron/usergroup.php</filename>, <filename>cronjobs/mail/mailing_lists_create.php</filename>, and <filename>cronjobs/mail/mailaliases.php</filename> but not before understanding the consequences.</para>
696 <title>Verifying the Installation</title>
697 <para>To verify if everything was installed correctly, use the browser and connect to GForge. You should see the GForge homepage. You will need to either disable CVS and SVN plugins in some way, or configure them before making the first test.</para>
699 <para>If you get an <computeroutput>Error: Could Not Connect to Database</computeroutput>, check if you have followed all installation instructions for the database. Also, you can experiment with making the settings in <filename>pg_hba.conf</filename> a bit more trusting - for example, change the last work of the second line from <literal>md5</literal> to <literal>trust</literal>.</para>
703 <title>Creating the Admin User</title>
704 <para>Site admins are anyone who is an admin of <literal>group_id</literal>=1.</para>
706 <listitem><para>Connect to GForge and register a new account.</para></listitem>
707 <listitem><para>Insert a valid email address; this will be used for the account confirmation.</para></listitem>
708 <listitem><para>Open your e-mail client, wait for the email from GForge site and follow the link that appears on the message.</para></listitem>
710 <para>Verify in Account Maintenance the user id of the user registered.</para>
711 <para>Usually this is 102, but you can verify this by running the following SQL query via the PostgreSQL <command>psql</command> utility:</para>
713 $ <userinput>psql -U gforge -W -h localhost gforge</userinput>
714 gforge=> <userinput>SELECT user_id FROM users WHERE user_name='<replaceable>YOUR USER NAME</replaceable>'</userinput>;
718 <para>Now set up the newly added user to be a GForge administrator:</para>
720 gforge=> <userinput>INSERT INTO user_group (user_id,group_id,admin_flags)</userinput>
721 gforge-> <userinput>VALUES (<replaceable>102</replaceable>,1,'A');</userinput>
726 <para>Once you have set up this user as an administrator, you can use GForge web interface to add more administrators.</para>
730 <title>Optional Features</title>
732 <title>JPGraph</title>
733 <para>PHP must be compiled with <literal>--with-gd</literal>, or appropriate package must be installed. Extra fonts for JPGraph are not necessary. Be sure your <filename>/etc/gforge/local.inc</filename> file contains the proper path to the <filename class="directory">jpgraph/src/</filename> directory.</para>
734 <para>Manual installation can be done like this:</para>
736 # tar -xzf jpgraph-1.19.tar.gz
737 # mkdir <replaceable>/var/www</replaceable>/jpgraph
738 # cp -R jpgraph-1.19/src/* <replaceable>/var/www</replaceable>/jpgraph
741 <para>If you want FHS-compliance, <filename class="directory">/usr/local/share/jpgraph</filename></para>
743 <para>When you get your preferred version of JPGraph installed, you will have to edit one setting in <filename>jpgraph.php</filename> (or <filename>jpg-config.php</filename>, depending on JPGraph version):</para>
745 DEFINE("USE_CACHE", false);
748 <para>Be careful with JPGraph license: versions > 1.5.2 are not free (as in free speech). You must check license before use.</para>
753 <para>If you want to use some of the Perl scripts that access the database, you'll need the <literal>DBI</literal> and <literal>DBD::Pg</literal> Perl modules. On Red Hat systems (and variants), you can get them by installing the <literal>libdbi</literal> and <literal>libdbd-pgsql</literal> packages. On Debian systems (and variants), the packages are called <literal>libdbi-perl</literal> and <literal>libdbd-pg-perl</literal>.</para>
754 <para>You'll also need to install <filename>utils/include.pl</filename> to <filename class="directory">/usr/lib/gforge/lib/</filename>, and put some configuration variables into <filename class="directory">/etc/gforge/local.pl</filename>. In particular, you'll need something like the following in <filename>local.pl</filename>:</para>
756 $sys_default_domain = 'gforge.company.com' ;
757 $sys_dbhost = '192.168.12.34' ;
758 $sys_dbname = 'gforge' ;
759 $sys_dbuser = 'gforge' ;
760 $sys_dbpasswd = 'p455w0rd' ;
764 <title>Jabber Support</title>
765 <para>GForge supports the sending of messages to jabber accounts. To accomplish this, you must have a user account setup on the jabber server that gforge can connect to and send messages.</para>
766 <para>Once you have that user account, server, and password set up, just edit <filename>/etc/gforge/local.inc</filename> and add the information to the jabber section.</para>
769 <title>Peer Ratings</title>
770 <para>Add yourself, and any others you wish, to the <quote>Peer Ratings</quote> project, which should be at <literal>/projects/peerrating/</literal> on the website. Make yourself an admininistrator of the project, and then proceed to <quote>rate</quote> other users on the website.</para>
771 <para>Members of the <quote>Peer Ratings</quote> project, who are administrator of the project, become the first trusted users. This is the only way to prime the pump for the peer ratings system.</para>
776 <title>Plugins</title>
778 <para>Since GForge 4.0, plugins are necessary as source code management is now provided by plugins (SCM* plugins).</para>
780 <para>For each plugin, you can find an <filename>INSTALL</filename> file in the plugin tarball.</para>
784 <title>Overview</title>
785 <para>CVS is now managed via the scmcvs plugin which is included in the <filename class="directory">plugins/</filename> directory in the tarball downloaded from gforge.org. Most of the files in scmcvs are intended for auto-installation on Debian systems and <emphasis role="strong">do not apply</emphasis> to the majority of users. The scmcvs plugin is activated by default in the <filename>gforge.sql</filename> database and all that you have to do is copy the <filename>plugins/scmcvs/etc/*</filename> directories to <filename class="directory">/etc/gforge</filename> directory and possibly modify the files slightly.</para>
788 <title>Cronjobs</title>
789 <para>Cronjobs for CVS are included in <filename>cronjobs/crontab.in</filename>, but are commented out by default for your security. The CVS cronjobs are in <filename><replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron</filename> and consist of:</para>
792 <para><filename>usergroup.php</filename> creates user and groups in <filename>/etc/passwd</filename>, <filename>/etc/shadow</filename>, and <filename>/etc/group</filename>.</para>
795 <para><filename>cvs.php</filename> creates repositories.</para>
798 <para><filename>ssh_create.php</filename> copies SSH keys to user directories.</para>
801 <para><filename>history_parse.php</filename> collects statistics.</para>
804 <para>Make sure these files are executed as root, and have proper execution bits set. Each of these cronjobs has configuration parameters which you may have to edit manually for your specific system. Here is a list of CVS cronjobs:</para>
805 <para>If you are using CVS 1.11, replace <literal>%1{sVv}</literal> in <filename><replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/cvs.php</filename> with <literal>%{sVv}</literal>, and replace <filename>syncmail</filename> with updated version:</para>
807 # <userinput>cd <replaceable>/var/www/gforge</replaceable></userinput>
808 # <userinput>cp plugins/scmcvs/bin/syncmail-cvs-1.11 cronjobs/cvs-cron/syncmail</userinput>
810 <para>If you are using CVS 1.12, replace <literal>%1{sVv}</literal> in <filename><replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/cvs.php</filename> with <literal>%s</literal>, and replace <filename>syncmail</filename> with updated version:</para>
812 # <userinput>cd <replaceable>/var/www/gforge</replaceable></userinput>
813 # <userinput>cp plugins/scmcvs/bin/syncmail-cvs-1.12 cronjobs/cvs-cron/syncmail</userinput>
817 <title>Installation</title>
819 <para>This guide doesn't cover chrooted CVS repositories which are always recommended.</para>
823 <para>Create default location for CVS repositories (<varname>$cvsdir_prefix</varname> in GForge configuration file):</para>
825 # <userinput>mkdir <replaceable>/cvsroot</replaceable></userinput>
829 <para><emphasis>Optional:</emphasis> Set up basic index.php file for CVS virtual host if desired. This guide has not further instructions on enabling CVS virtual host.</para>
831 # <userinput>mkdir <replaceable>/var/www/cvs</replaceable></userinput>
832 # <userinput>cp <replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/www/* <replaceable>/var/www/cvs</replaceable></userinput>
836 <para>If you want to use checkout of svmcvs plugin, copy it:</para>
838 # <userinput>mkdir <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs</userinput>
839 # <userinput>cp -R <replaceable>gforge-plugin-scmcvs</replaceable>/* <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs</userinput>
841 # <userinput>mkdir <replaceable>/var/www/gforge</replaceable>/www/plugins/scmcvs</userinput>
842 # <userinput>cp -R <replaceable>gforge-plugin-scmcvs</replaceable>/www/* <replaceable>/var/www/gforge</replaceable>/www/plugins/scmcvs</userinput>
846 <para>Copy the scmcvs plugin config to <filename class="directory">/etc/gforge</filename>:</para>
848 # <userinput>cp -R <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/etc/* /etc/gforge</userinput>
852 <para>Make sure the cvs crons are executable:</para>
854 # <userinput>cd <replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/</userinput>
855 # <userinput>chmod 755 *.php *.sh</userinput>
859 <para>Copy CVS restricted shell:</para>
861 # <userinput>cp <replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/cvssh.pl /bin</userinput>
865 <para>Edit GForge Config File <filename>/etc/gforge/local.inc</filename> and change <varname>$sys_path_to_scmweb</varname> to be <filename class="directory"><replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/cgi-bin</filename>.</para>
868 <para>You may have to edit <filename>/etc/gforge/plugins/scmcvs/cvsweb.conf</filename> to change the cvsroot location:</para>
870 'gforge' => ['GForge-CVS', '<replaceable>/home/chroot/cvsroot/</replaceable>'],
874 <para>Install the following non-core Perl modules:</para>
877 <para>IPC::Run</para>
880 <para>URI::Escape</para>
885 <para>You may want to user CVS pserver. First, assure that cvspserver service is defined in <filename>/etc/services</filename>. It will look like this:</para>
890 <para>Add entry for pserver in <filename>/etc/inetd.conf</filename>:</para>
891 <para><literal>cvspserver stream tcp nowait root <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/bin/cvs-pserver cvs-pserver</literal></para>
893 <para>Make sure that the wrapper script is executable:</para>
895 # <userinput>chmod +x <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/bin/cvs-pserver</userinput>
897 <para>The used wrapper script <filename><replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/bin/cvs-pserver</filename> assumes that CVS repositories are in chroot environment and you may want to edit the script and change <varname>CHROOTDIR</varname> and <varname>CVSROOT</varname> variables.</para>
899 <para>CVS pserver has long history of vulnerabilities and its use is highly discouraged.</para>
906 <title>CVSTracker</title>
908 <title>Overview</title>
909 <para>The cvstracker plugin allows for some integration between CVS commits and the bug tracker and task manager. So, for example, when you commit, you can reference bug and task IDs in your commit message and have the commit linked to the corresponding bug and task.</para>
910 <para>See the <filename>plugins/cvstracker/README</filename> file for details. This plugin is enabled by default in the <filename>gforge.sql</filename> database file. As with the other plugins, you may manually place the config files in <filename class="directory">/etc/gforge/plugins/cvstracker/</filename> and uncomment the cronjob in <filename>crontab.in</filename>.</para>
911 <para>You will also have to copy the <filename>newcommit.php</filename> file to your gforge <filename class="directory">www/plugins/cvstracker/</filename> dir</para>
914 <title>Installation</title>
916 #copy the cvstracker config files to /etc/gforge/
917 cd <replaceable>/var/www/gforge</replaceable>/plugins/cvstracker/
918 cp -R etc/plugins/cvstracker/ /etc/gforge/plugins/
919 mkdir <replaceable>/var/www/gforge</replaceable>/www/plugins/cvstracker/
920 cp -R www/* <replaceable>/var/www/gforge</replaceable>/www/plugins/cvstracker/
922 <para><filename>plugins/cvstracker/bin/post.php</filename> is called on each commit and it needs the GForge configuration file <filename>local.inc</filename> so the latter should have relaxed permissions.</para>
923 <para>Uncomment <filename>update_loginfo.php</filename> in crontab.</para>
924 <para>Fix CVSTracker table:</para>
926 $ <userinput>psql -U gforge -W -h localhost gforge</userinput>
927 template1=# <userinput>ALTER TABLE public.plugin_cvstracker_data_master DROP cvs_date;</userinput>
928 template1=# <userinput>ALTER TABLE public.plugin_cvstracker_data_master ADD cvs_date INT;</userinput>
929 template1=# <userinput>ALTER TABLE public.plugin_cvstracker_data_master ALTER cvs_date SET NOT NULL;</userinput>
932 <para>CVS Tracker is not enabled by default for project. You'll have to manually enable it.</para>
939 <title>Overview</title>
940 <para>SVN is also managed via plugin – the scmsvn plugin is included and activated by default in GForge. As with scmcvs, you have to move the <filename>scmcvs/etc/plugins/*</filename> files to <filename>/etc/gforge/plugins/*</filename> and may have to make minor modifications for your specific setup.</para>
941 <para>There are two ways to manage SVN – one is to have SVN over DAV and the other is to have SVN over SSH just as you do with CVS. If you choose to use DAV, you will need the <filename class="libraryfile">mod_auth_gforge</filename> library compiled and installed in your apache and the appropriate virtual host settings in your <filename>httpd.conf</filename>. <filename class="libraryfile">mod_auth_gforge</filename> is available from gforge.org. The cronjobs to manage SVN are in <filename class="directory">cronjobs/dav-svn/</filename> and so are sample <filename>httpd.conf</filename> virtual host settings. Each of these cronjobs has configuration parameters which you may have to edit manually for your specific system.</para>
942 <para>Configuring svnserv for svn-over-ssh:
945 <para><ulink url="http://svnbook.red-bean.com/en/1.0/ch06s03.html" /></para>
948 <para><ulink url="http://www.logemann.org/day/archives/000099.html" /></para>
951 <para><ulink url="http://bitworking.org/news/Getting_subversion_svn_ssh____to_work_with_PuTTY" /></para>
957 <title>Installation</title>
959 <para><emphasis>Instructions here are far from complete.</emphasis></para>
962 #Create default location for SVN repositories
965 # Optional - Set up some basic files for SVN-over-DAV only
967 cp <replaceable>/var/www/gforge</replaceable>/cronjobs/dav-svn/www/* /var/www/svn/
969 #copy the scmsvn config files to /etc/gforge/
970 cp -R gforge/plugins/scmsvn/etc/plugins/scmsvn/ /etc/gforge/plugins/
976 <title>Upgrading Existing Install</title>
977 <para>You will upgrade your database from a prior version by applying each database schema change, in order, and applying it only once. Only apply the schema changes in the <filename class="directory">db/</filename> folder that are dated <emphasis>after</emphasis> your existing installation.</para>
978 <para>There may also be migration scripts that have to be run. In the <filename class="directory">db/</filename> folder, look for php scripts and run them.</para>
980 <para>You have to apply database schema changes and to run migration scripts in the right order.</para>
984 <title>Most Common Problems</title>
985 <para>Q: I get a blank page when I visit http://gforge.company.com/</para>
986 <para>A: Most often you are missing the php-pgsql library that lets PHP talk to the postgres database. Find a php-pgsql RPM or recompile php to have pgql support.</para>
987 <para>If you're sure you have php-pgsql support, you can edit common/include/database.php and remove the @ symbol from this line:</para>
991 <para>So that it looks like:</para>
995 <para>This will let debug output dump to the screen and may let you find the problem. Search the forums for more solutions.</para>
997 <para>Q: <quote>Error Occurred In the Logger</quote> or other database permission problems</para>
998 <para>A: As stated in the installation instructions, the database must be created, owned, and accessed by the gforge user. This user is the only one who will have total acess to all the tables. Any other user would have to be specifically granted permissions with the GRANT commands in postgres.</para>
1000 <para>Q: Reporting or time tracking doesn't work</para>
1002 <para>A: Go to the reporting tab and scroll down so you can choose <quote>Initialize/Rebuild Reporting Tables</quote></para>
1004 <para>You may also be missing GD support or be missing JPGraph or have it installed improperly. The <filename class="directory">jpgraph/src/</filename> directory should be specified accurately in your <filename class="directory">local.inc</filename> file, and you should include a <filename>/</filename> at the end of the path specified. In addition, you should modify <filename>jpgraph.php</filename> to set <literal>USE_CACHE=false</literal>.</para>
1006 <para>Q: How do I upgrade my database?</para>
1007 <para>A: As stated above, you must apply the changes that are listed in date order in the <filename class="directory">db/</filename> directory to your database. Only the changes that are not already in your old <filename class="directory">db/</filename> directory should be applied, and they should be applied and checked <emphasis>in order</emphasis>.</para>
1009 <para>Q: I'm getting an error about BaseLanguage.class not being found.</para>
1010 <para>A: Make sure your localization path is correctly specified in the local.inc file and that it is readable <emphasis>and</emphasis> writable by the apache user.</para>
1012 <para>Q: When I click on <quote>/projects/</quote> or <quote>/users/</quote> links, I get the source code instead of the page I expected.</para>
1013 <para>A: As shown in the example <filename>httpd.conf</filename> files above, you may have to switch to using the <literal><Files></literal> or <literal><Location></literal> directives depending on your server version.</para>
1015 <para>Q: How do I backup GForge?</para>
1016 <para>A: The only proper way to backup the gforge database is with <command>pg_dump</command>. Any attempt to backup the filesystem while pgsql is running will result in a useless and corrupt backup. You can backup CVS trees using <command>tar</command> as long as they are not actively and heavily used during the backup. Mailman and the FRS uploads dir can also be backed up with <command>tar</command>.</para>
1018 <para>Q: Any time i enter an apostrophe in a text box, i get a parse error</para>
1019 <para>A: As stated in the instructions above, you should have <literal>magic_quotes_gpc=On</literal> in your <filename>php.ini</filename> file.</para>
1021 <para>Q: Large uploads into FRS or the doc manager fail.</para>
1022 <para>A: Apache and the <filename>php.ini</filename> file need to have upload limits and possibly memory limits increased.</para>