1 <?xml version='1.0' encoding='UTF-8'?>
2 <!-- This document was created with Syntext Serna Free. --><!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "../../../dtd/docbookx.dtd" [
3 <!ENTITY % authors SYSTEM "../entities/authors.ent">
6 <article id="installation_guide" lang="en-US">
8 <title>FusionForge Installation Guide</title>
10 &reinhard_spisser;&tom_copeland;&ognyan_kulev;&guillaume_smet; </authorgroup>
13 <title>Hardware Requirements</title>
15 Hardware requirements are dependent on the number of users that will use the system and how active those users are.
18 For instance, an installation of FusionForge hosts over 450 users and over 140 projects on a single CPU Pentium 2.4GHz machine with 512 MB of RAM.
21 You can find additionnal information about hardware used by several installations of GForge in the <ulink url="http://gforge.org/gf/download/docmanfileversion/105/1798/gforge-sites.html">old GForge sites list that used to be maintained by Tom Copeland</ulink>.
25 <title>Software Requirements</title>
27 FusionForge should work correctly on any system configured like this:
31 <para>GNU/Linux Operating System</para>
34 <para><ulink url="http://www.postgresql.org/">PostgreSQL</ulink> 8.3 or later (8.1, 8.2 should work)</para>
37 <para><ulink url="http://www.apache.org/">Apache</ulink> 2.2 or later</para>
40 <para><ulink url="http://www.openssl.org/">openssl</ulink> 0.9.4 or later</para>
43 <para><ulink url="http://www.openssl.org/">mod_ssl</ulink> 2.4.10 or later (included in Apache 2.0 and later)</para>
46 <para><ulink url="http://www.php.net/">PHP</ulink> 5.2 or later (php5.1 should work)</para>
49 <para>php-pgsql (enable it with <literal>--with-pgsql</literal> when building PHP, or install it as package)</para>
52 <para>php-mbstring (enable it with <literal>--with-mbstring</literal> when building PHP, or install it as package)</para>
55 <para><ulink url="http://htmlpurifier.org/">htmlpurifier</ulink> 4.0 or later</para>
63 <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>
66 <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>
69 <para><ulink url="http://jabberd.jabberstudio.org/">Jabberd</ulink> (Jabber support)</para>
72 <para><ulink url="http://www.aditus.nu/jpgraph/">JPGraph</ulink> (Gantt Charting and Graphing Support)</para>
75 <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>
79 Successful installations and operations have been done using the following systems:
83 <para>Debian GNU/Linux 5.0 (Lenny)</para>
89 <para>RedHat Enterprise Linux 5</para>
94 <title>Installation</title>
96 <title>Overview</title>
98 <para>The <filename>INSTALL</filename> file in FusionForge package and <filename>README</filename> files in plugin directories are the authoritative sources for installation instructions and they should have more precedence over this guide.</para>
101 <para>This installation guide is for FusionForge 5.0.</para>
103 <para>FusionForge 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>
104 <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>
105 <para>The manual installation of FusionForge 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 FusionForge forums where little help is available.</para>
108 <title>Installing FusionForge on Debian</title>
109 <!-- FIXME : this is absolete now and should be fixed --> <para>
110 You can simply add lines found at <ulink url="http://debian.fusionforge.org/"/> to <filename>/etc/apt/sources.list</filename> and type <command>apt-get install fusionforge</command> to install a working FusionForge system, thanks to Christian Bayle and Roland Mas.
113 Note that FusionForge will soon be part of official Debian, and so you will find it in all debian mirrors all other the planet. Package versions of FusionForge may lag behind upstream versions. From scratch install snapshot are also available for a guided installation.
117 <title>Installing FusionForge on RPM-based systems</title>
118 <para>RPM should be available soon, see <ulink url="http://fusionforge.org/"/> website for availability.</para>
121 <title>Installing FusionForge oneself on a linux distribution</title>
122 <para>To install FusionForge, follow these steps (as root):</para>
124 <title>Directory Layout</title>
125 <para>Instructions below assume that gforge is unpacked into <filename class="directory">
126 <replaceable>/opt/gforge</replaceable>
127 </filename>. There are some other directories where FusionForge stores files. In this installation guide, they are put in <filename class="directory">/var/www</filename> too.</para>
129 <para>If you want to be <ulink url="http://www.pathname.com/fhs/">FHS</ulink>-compliant, FusionForge 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>
133 <title>Getting the source</title>
134 <para>There is two ways to get the sources from FusionForge : </para>
135 <!-- FIXME : this is absolete now and should be fixed --> <screen>
136 # <userinput>tar -xjvf fusionforge-5.0.tar.bz2</userinput>
137 # <userinput>cd fusionforge-5.0</userinput>
138 # <userinput>mkdir -p /opt/gforge</userinput>
139 # <userinput>cp -r *<replaceable>/opt/gforge</replaceable></userinput>
143 <title>Checking out from the SVN repository with tag v5_0 </title>
144 <para>Alternative way to get FusionForge 5.0 is to check out with tag v5_0 from SVN. This gets latest fixes as well.</para>
146 $ <userinput>svn checkout --username anonsvn svn://scm.fusionforge.org/svnroot/fusionforge/tags/v5_0 fusionforge-5.0</userinput>
148 $ <userinput>cd fusionforge</userinput>
149 $ <userinput>cd gforge/www/plugins</userinput>
150 $ <userinput>ln -s ../../plugins/scmcvs/www scmcvs</userinput>
151 $ <userinput>ln -s ../../plugins/scmsvn/www scmsvn</userinput>
152 $ <userinput>ln -s ../../plugins/cvstracker/www cvstracker</userinput>
155 <title>Fixing access rights</title>
156 <para>You may want to make sure that permissions are correct (replace <replaceable>apache-group</replaceable> with the system group used by Apache server):</para>
158 # <userinput>cd /opt/gforge</userinput>
159 # <userinput>chown -R root:<replaceable>apache-group</replaceable> .</userinput>
160 # <userinput>chmod -R 644 .</userinput>
161 # <userinput>find -type d | xargs chmod 755</userinput>
162 # <userinput>chmod -R 755 cronjobs</userinput>
167 <title>FusionForge Config File</title>
168 <para>In the FusionForge 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>
170 # <userinput>mkdir /etc/gforge</userinput>
171 # <userinput>chown root: /etc/gforge</userinput>
172 # <userinput>chmod 755 /etc/gforge</userinput>
173 # <userinput>cp <replaceable>/opt/gforge</replaceable>/etc/local.inc.example /etc/gforge/local.inc</userinput>
174 # <userinput>chown <replaceable>apache-user</replaceable>:<replaceable>apache-group</replaceable> /etc/gforge/local.inc</userinput>
175 # <userinput>chmod 600 /etc/gforge/local.inc</userinput>
179 <title>Configuring FusionForge</title>
180 <para>Open <filename>/etc/gforge/local.inc</filename>, configuring the following basic parameters:</para>
183 <para>Database configuration:</para>
185 $sys_dbhost="localhost"
186 $sys_dbname="gforge"
187 $sys_dbuser="gforge"
188 $sys_dbpasswd="<replaceable>gforge-password</replaceable>"
192 <para>Change the following basic variables::</para>
194 $sys_urlroot="<replaceable>/var/www/gforge</replaceable>/www/";
195 $sys_themeroot="<replaceable>/var/www/gforge</replaceable>/www/themes/";
196 $sys_plugins_path="<replaceable>/var/www/gforge</replaceable>/plugins/";
198 </listitem>--> <listitem>
199 <para>The directive <varname>$sys_default_domain</varname> should contain the domain of your server, e.g. <literal>gforge.<replaceable>company.com</replaceable></literal>. You may want to replace all occurences of <replaceable>company.com</replaceable> with company's domain name.</para>
205 <title>Configuring the Database (PostgreSQL)</title>
207 <title>PostgreSQL Requirements</title>
208 <para>You to have installed the following packages for </para>
211 <para>a CentOS or Red Hat 5 or Fedora: postgresql, postgresql-libs, postgresql-server, postgresql-contrib</para>
214 <para>a Debian: postgresql, postgresql-contrib</para>
219 <title>Initialization of PostgreSQL</title>
220 <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>
222 # <userinput>su - postgres</userinput>
223 $ <userinput>initdb</userinput>
226 <para>This will wipe out any existing PostgreSQL databases!</para>
230 <title>PostgreSQL Authentication Configuration</title>
231 <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>
233 # <userinput>/etc/init.d/postgresql restart</userinput>
234 # <userinput>su - postgres</userinput>
235 $ <userinput>psql template1</userinput>
237 <para>If connection fails, add the following line to <filename>pg_hba.conf</filename>:</para>
239 local all postgres ident sameuser
241 <para>FusionForge 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> (before other <literal>host</literal> directives):</para>
243 host gforge gforge 127.0.0.1 255.255.255.255 md5
245 <para>This line assumes that FusionForge will always use local PostgreSQL database (<literal>localhost</literal>). If this is not the case, consult PostgreSQL manual for ways to allow connection.</para>
246 <!-- <para>The following option should be set in <filename>postgresql.conf</filename> because connection to <literal>localhost</literal> uses TCP/IP:</para>
249 </screen>--> <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>
251 # <userinput>/etc/init.d/postgresql restart</userinput>
255 <title>Importing Database</title>
256 <para>Create FusionForge database user:</para>
257 <!-- TODO : should probably use fusionforge and not gforge below, now --> <screen>
258 # <userinput>su - postgres</userinput>
259 $ <userinput>psql template1</userinput>
260 template1=# <userinput>CREATE USER gforge NOCREATEUSER NOCREATEDB</userinput>
261 template1-# <userinput>PASSWORD '<replaceable>gforge-password</replaceable>';</userinput>
263 <para>Create FusionForge database:</para>
265 template1=# <userinput>CREATE DATABASE gforge OWNER gforge ENCODING 'UNICODE';</userinput>
266 template1=# <userinput>\q</userinput>
268 <para>Add PL/pgSQL support using the commands:</para>
270 <!-- # <userinput>su - postgres</userinput> -->
271 $ <userinput>createlang plpgsql gforge</userinput>
273 <para>Finally, install the database:</para>
275 $ <userinput>cd <replaceable>/opt/gforge</replaceable>/db</userinput>
276 $ <userinput>psql -a -U gforge -W -h localhost -f gforge.sql gforge &> /tmp/gforge.sql.log</userinput>
279 <para>You may experience the following errors. They are harmless and you can safely ignore them:</para>
281 ERROR: permission denied for language c
282 ERROR: must be superuser to create procedural language
283 ERROR: permission denied for schema public
289 <title>Configuring DNS Server (BIND)</title>
290 <para>FusionForge needs its own domain. In example FusionForge configuration file, it's <literal>gforge.<replaceable>company.com</replaceable></literal><!-- TODO: s/gforge/fusionforge/g -->. You should search for <replaceable>company.com</replaceable> in example FusionForge configuration file and replace it with your domain name.</para>
291 <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 FusionForge 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>
292 <para>For DNS, you need to have the bind package installed</para>
293 <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>
295 gforge IN NS ns.gforge.<replaceable>company.com</replaceable>.
296 ns.gforge IN A <replaceable>1.2.3.4</replaceable>
299 <para>Do not add the latter resource record (<literal>ns.gforge</literal>) if this DNS server serves both <literal>
300 <replaceable>company.com</replaceable>
301 </literal> and <literal>gforge.<replaceable>company.com</replaceable></literal> zones.</para>
303 <para>New zone file for <literal>gforge.<replaceable>company.com</replaceable></literal> may look like this:</para>
306 @ IN SOA gforge.<replaceable>company.com</replaceable>. hostmaster.gforge.<replaceable>company.com</replaceable>. (
311 3600 ) ; Negative Cache TTL
313 @ IN NS ns.gforge.<replaceable>company.com</replaceable>.
314 @ IN A <replaceable>1.2.3.4</replaceable>
315 ns IN A <replaceable>1.2.3.4</replaceable>
317 download IN A <replaceable>1.2.3.4</replaceable>
318 shell IN A <replaceable>1.2.3.4</replaceable>
319 users IN A <replaceable>1.2.3.4</replaceable>
320 lists IN A <replaceable>1.2.3.4</replaceable>
321 cvs IN A <replaceable>1.2.3.4</replaceable>
322 svn IN A <replaceable>1.2.3.4</replaceable>
323 scm IN A <replaceable>1.2.3.4</replaceable>
324 ldap IN A <replaceable>1.2.3.4</replaceable>
325 jabber IN A <replaceable>1.2.3.4</replaceable>
327 <para>The new zone must be added in main BIND configuration file:</para>
329 zone "gforge.<replaceable>company.com</replaceable>" {
331 file "<replaceable>/dist-specific/path/to/zone-file</replaceable>";
334 <para>Of course, changes will take effect after reloading BIND.</para>
335 <para>It is required that the dns service is up on each reboot.</para>
337 $ <userinput>chkconfig named on</userinput>
340 <title>Basic but concrete DNS cofiguration on CentOS, Fedora or Red Hat</title>
341 <para>Create the file <filename>/etc/named.conf</filename> and add in :</para>
344 directory "/var/named";
345 dump-file "/var/named/data/cache_dump.db";
346 statistics-file "/var/named/data/named_stats.txt";
348 include "/etc/rndc.key";
352 file "/var/named/root.db";
354 zone "gforge.company.com" {
356 file "/var/named/gforge.db";
359 <para>Create the file <filename>/var/named/named.root</filename>and add in :</para>
364 </section>--> </section>
366 <title>Configuring PHP</title>
367 <para>Make sure you have installed <literal>pgsql</literal> and <literal>mbstring</literal> modules.</para>
368 <para>PHP is used in two ways:</para>
371 <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 the document. If you prefer to configure <filename>php.ini</filename>, the following directives are required by FusionForge:</para>
373 <!-- register_globals = Off-->
374 magic_quotes_gpc = Off
376 include_path=".:<replaceable>/opt/gforge</replaceable>:<replaceable>/opt/gforge</replaceable>/www/include:/etc/gforge"
380 <para><emphasis>Cron jobs and some scripts</emphasis> require PHP Command-Line Interface (CLI). Scripts are usually invoked with command like this:</para>
382 $ <userinput>php5 -f cronjobs/mail/mailing_lists_create.php</userinput>
385 <para>The <literal>-f</literal> is optional when using PHP CLI but it's required when PHP CGI executable is used.</para>
387 <para>You must set <varname>include_path</varname> in PHP CLI <filename>php.ini</filename>, like already shown above. Increase <varname>memory_limit</varname> configuration parameter to at least 32M. To find where <filename>php.ini</filename> is located, use the following command:</para>
389 $ <userinput>php5 -i | fgrep php.ini</userinput>
394 <section id="web-server">
395 <title>Configuring the Web Server (Apache)</title>
396 <para>Find what system user and group are used by Apache server and change <varname>$sys_apache_user</varname> and <varname>$sys_apache_group</varname> (in FusionForge configuration) respectively in /etc/gforge/local.inc.</para>
397 <para>You should decide where to put FusionForge 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>
398 <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 FusionForge virtual host configuration for Apache from scratch. All is inside the following template:</para>
400 NameVirtualHost <replaceable>1.2.3.4</replaceable>
401 <VirtualHost <replaceable>1.2.3.4</replaceable>>
403 <replaceable># Put the rest of the directives here.</replaceable>
408 <para>Configuring for SSL is not discussed in this guide.</para>
412 <para>Set basic virtual host settings:</para>
414 ServerName gforge.<replaceable>company.com</replaceable>
415 ServerAdmin webmaster@gforge.<replaceable>company.com</replaceable>
419 <para>Define log files:</para>
421 CustomLog "<replaceable>/var/log/gforge</replaceable>/gforge/access.log" combined
422 ErrorLog "<replaceable>/var/log/gforge</replaceable>/gforge/error.log"
424 <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>
426 CustomLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/gforge/%Y/%m/%d/access.log" combined
427 ErrorLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/gforge/%Y/%m/%d/error.log"
430 <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>
434 <para>Set up document root:</para>
436 DocumentRoot "<replaceable>/opt/gforge</replaceable>/www"
437 <Directory "<replaceable>/opt/gforge</replaceable>/www">
438 Options FollowSymLinks
442 ErrorDocument 404 /404.php
447 <para>Configuring PHP for Apache</para>
448 <para>Ensure that PHP module is loaded (this is automaticaly made when you install php with rpm or deb). You may need to consult your distribution manual. Typical lines that load and configure PHP module are like this:</para>
450 LoadModule php_module modules/libphp.so
453 AddType application/x-httpd-php .php
455 <para>Insert the following instructions after the <literal>DocumentRoot</literal> directive:</para>
457 <Location /projects>
458 ForceType application/x-httpd-php
460 <Location /users>
461 ForceType application/x-httpd-php
465 <para>If you use Apache 2, you may need to use a different configuration. Usually, this is not needed. If you receive a <computeroutput>Page Not Found</computeroutput> summary pages, you better try this different style of configuring.</para>
466 <para>Change the existing <literal>Files</literal> directive to:</para>
472 LimitRequestBody 2097152
475 <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>
476 <para>Add the following lines:</para>
478 <Files projects>
493 <para>Set up PHP module:</para>
494 <para>If the register_globals variable is set to On in your php.ini, add this line in your conf apache :</para>
496 php_flag register_globals Off
498 <para>If the files_uploads variable is not set to On in your php.ini, add this line in your conf apache :</para>
500 php_flag files_uploads On
502 <para>If the AddDefaultCharset variable is not set to UTF-8 in your httpd.conf, add this line in your conf apache :</para>
504 php_value default_charset "UTF-8"
506 <para>Add these lines in your conf apache </para>
508 php_flag magic_quotes_gpc Off
509 php_value include_path ".:/etc/gforge:<replaceable>/opt/gforge</replaceable>:<replaceable>/opt/gforge</replaceable>/www/include"
513 <para>Set up directory index script name (this is automaticaly made when you install php with rpm or deb) :</para>
515 DirectoryIndex index.php
519 <para>Of course, all changes will take effect only after reloading or restarting Apache.</para>
522 <title>Configuring Mail Transport Agent (Any)</title>
523 <para>Add the following line to <filename>/etc/aliases</filename> and run <command>newaliases</command>:</para>
527 <para>Make sure that the following domain names are accepted as local destinations by mail transport agent:</para>
528 <!-- TODO: s/gforge/fusionforge/g --> <itemizedlist>
530 <para><literal>gforge.<replaceable>company.com</replaceable></literal></para>
533 <para><literal>lists.gforge.<replaceable>company.com</replaceable></literal></para>
536 <para><literal>users.gforge.<replaceable>company.com</replaceable></literal></para>
539 <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>
541 <title>Mail gateways to forum and tracker</title>
542 <para>When forum or tracker is monitored, replying to monitor mails are processed by mail gateways. These gateways use FusionForge 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>
546 <title>File Release System (FRS)</title>
547 <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 FusionForge Config File <filename>/etc/gforge/local.inc</filename> as <varname>$sys_upload_dir</varname>.</para>
549 # <userinput>mkdir <replaceable>/var/lib/gforge</replaceable>/download</userinput>
550 # <userinput>chown -R <replaceable>apache-user</replaceable><replaceable>/var/lib/gforge</replaceable>/download</userinput>
553 <para>For FHS-compliance, use <filename class="directory">/var/local/gforge/download</filename>.</para>
557 <title>Configuring GNU Mailman</title>
558 <para>GNU Mailman is used to help manage the FusionForge 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 FusionForge configuration variable <varname>$sys_path_to_mailman</varname> to that Mailman directory.</para>
559 <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>
560 <para>For all problems with Mailman installation and use, contact the Mailman mailing lists for help.</para>
561 <para>To install it:</para>
564 <para>Install a GNU Mailman package or compile it</para>
567 <para>Don't integrate Mailman with Postfix (or other MTA) by delegating it generation of alias-style file. FusionForge 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>
569 # <userinput><replaceable>/usr/lib/mailman/bin</replaceable>/newlist mailman</userinput>
573 <para>Configure <filename>mm_cfg.py</filename>:</para>
576 <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>
579 <para>Strip ugly <literal>cgi-bin</literal> from URLs in configuration parameters.</para>
584 <para><command>su</command> to <literal>root</literal> and set the Mailman password by using the <command>mmsitepass</command> command</para>
587 <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>
590 <para>In Web server configuraton, create virtual host for Mailman, adjusting <literal>ScriptAlias</literal> and <literal>Alias</literal> directives:</para>
592 <VirtualHost <replaceable>1.2.3.4</replaceable>>
593 ServerName lists.gforge.<replaceable>company.com</replaceable>
594 ServerAdmin webmaster@gforge.<replaceable>company.com</replaceable>
596 # You may want to add these files to logrotate, or just use cronolog as shown below
597 CustomLog "<replaceable>/var/log/gforge</replaceable>/lists/access.log" combined
598 ErrorLog "<replaceable>/var/log/gforge</replaceable>/lists/error.log"
600 # CustomLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/lists/%Y/%m/%d/access.log" combined
601 # ErrorLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/lists/%Y/%m/%d/error.log"
603 DocumentRoot <replaceable>/var/www/mailman</replaceable>
604 DirectoryIndex index.html
605 ScriptAlias /mailman/ <replaceable>/usr/lib/cgi-bin/mailman/</replaceable>
606 Alias /pipermail/ <replaceable>/var/lib</replaceable>/mailman/archives/public/
607 Alias /images/ <replaceable>/usr/share/images/</replaceable>
611 <para>Check that <literal>ScriptAlias</literal> and <literal>Alias</literal> directories are correct. The example values are for Debian 3.1 (Sarge).</para>
616 <title>Mailing list for commits</title>
617 <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>
621 <title>Source Code Management (SCM)</title>
622 <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>
624 # <userinput>mkdir <replaceable>/var/www</replaceable>/scmtarballs</userinput>
625 # <userinput>mkdir <replaceable>/var/www</replaceable>/scmsnapshots</userinput>
627 <para>These directories correspond to FusionForge configuration variables <varname>$sys_scm_tarballs_path</varname> and <varname>$sys_scm_snapshots_path</varname>.</para>
629 <para>For FHS-compliance, use <filename class="directory">/var/local/gforge/scmtarballs</filename> and <filename class="directory">/var/local/gforge/scmsnapshots</filename>.</para>
633 <title>Cron Jobs</title>
635 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.
638 <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.
641 <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.
643 <para>Prepare for <filename>cronjobs/cvs-cron/usergroup.php</filename> and <filename>cronjobs/mail/mailaliases.php</filename>.</para>
645 # <userinput>adduser anonymous</userinput>
646 # <userinput>cp /etc/aliases /etc/aliases.org</userinput>
647 # <userinput>cp /etc/shadow /etc/shadow.org</userinput>
648 # <userinput>cp /etc/passwd /etc/passwd.org</userinput>
649 # <userinput>cp /etc/group /etc/group.org</userinput>
652 <para>There are two other ways to authenticate FusionForge users: LDAP and NSS with PostgreSQL backend. They are not discussed in this guide.</para>
655 <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>
659 The following command will blow away any existing root crontab:
663 # <userinput>crontab cronjobs/crontab.in</userinput>
665 <para>Now edit the paths to the cron scripts by setting the value of <varname>GFORGE</varname> and <varname>PHP</varname> variables:</para>
667 # <userinput>crontab -e</userinput>
669 <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>
672 <title>Verifying the Installation</title>
673 <para>To verify if everything was installed correctly, use the browser and connect to FusionForge. You should see the FusionForge homepage. You will need to either disable CVS and SVN plugins in some way, or configure them before making the first test.</para>
675 <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>
679 <title>Creating the Admin User</title>
680 <para>Site admins are anyone who is an admin of <literal>group_id</literal>=1.</para>
683 <para>Connect to FusionForge and register a new account.</para>
686 <para>Insert a valid email address; this will be used for the account confirmation.</para>
689 <para>Open your e-mail client, wait for the email from FusionForge site and follow the link that appears on the message.</para>
692 <para>Verify in Account Maintenance the user id of the user registered.</para>
693 <para>Usually this is 102, but you can verify this by running the following SQL query via the PostgreSQL <command>psql</command> utility:</para>
695 $ <userinput>psql -U gforge -W -h localhost gforge</userinput>
696 gforge=> <userinput>SELECT user_id FROM users WHERE user_name='<replaceable>YOUR USER NAME</replaceable>'</userinput>;
700 <para>Now set up the newly added user to be a FusionForge administrator:</para>
702 gforge=> <userinput>INSERT INTO user_group (user_id,group_id,admin_flags)</userinput>
703 gforge-> <userinput>VALUES (<replaceable>102</replaceable>,1,'A');</userinput>
707 <para>One of the first string as FusionForge administrator is to initialize once the reporting tables from Reporting tab.</para>
709 <para>Once you have set up this user as an administrator, you can use FusionForge web interface to add more administrators.</para>
713 <title>Customizing Front Page</title>
714 <para>If you want to customize front page, you'll have to provide new <filename>index_std.php</filename>:</para>
717 <para>Create <filename class="directory">/etc/gforge/custom</filename> directory.</para>
720 <para>Set <varname>$sys_custom_path</varname> configuration variable to <filename class="directory">/etc/gforge/custom</filename>.</para>
723 <para>Copy <filename><replaceable>/usr/share/gforge</replaceable>/www/index_std.php</filename> to <filename>/etc/gforge/custom/index_std.php</filename> and edit it as you like.</para>
728 <title>Optional Features</title>
730 <title>Project webs</title>
731 <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 FusionForge 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>
733 <title>DNS Server Configuration (BIND)</title>
734 <para>Project virtual hosts require new DNS zone. Making this new zone is similar to making DNS zone for FusionForge itself.</para>
737 <para>Declare new zone in <literal>gforge.<replaceable>company.com</replaceable></literal> zone:</para>
739 projects IN NS ns.projects.gforge.<replaceable>company.com</replaceable>
741 <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>
743 ns.projects IN A <replaceable>1.2.3.4</replaceable>
745 <para>Don't forget to change serial number of <literal>gforge.<replaceable>company.com</replaceable></literal> zone!</para>
748 <para>Create new zone file with following content:</para>
751 @ IN SOA projects.gforge.<replaceable>company.com</replaceable>. hostmaster.gforge.<replaceable>company.com</replaceable>. (
756 3600 ) ; Negative Cache TTL
758 @ IN NS ns.projects.gforge.<replaceable>company.com</replaceable>.
759 @ IN A <replaceable>1.2.3.4</replaceable>
760 ns IN A <replaceable>1.2.3.4</replaceable>
762 * IN A <replaceable>1.2.3.4</replaceable>
766 <para>The new zone must be added in main BIND configuration file:</para>
768 zone "projects.gforge.<replaceable>company.com</replaceable>" {
770 file "<replaceable>/dist-specific/path/to/zone-file</replaceable>";
775 <para>Reload BIND and test if all works:</para>
777 $ <userinput>host test.projects.gforge.<replaceable>company.com</replaceable></userinput>
778 test.projects.gforge.<replaceable>company.com</replaceable> has address <replaceable>1.2.3.4</replaceable>
784 <title>Web Server Configuration (Apache)</title>
785 <para>Module <literal>vhost_alias</literal> should be enabled and the following directives should be added to <filename>httpd.conf</filename> (if <filename class="directory"><replaceable>/var/www/homedirs</replaceable>/groups</filename> is what you have chosen in <varname>$groupdir_prefix</varname>):</para>
787 <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>
791 # WARNING - security is degraded by having this
792 # on the same machine as the primary FusionForge
794 NameVirtualHost <replaceable>1.2.3.4</replaceable>
795 <VirtualHost <replaceable>1.2.3.4</replaceable>>
796 ServerName projects.gforge.<replaceable>company.com</replaceable>
797 ServerAlias *.projects.gforge.<replaceable>company.com</replaceable>
798 ServerAdmin webmaster@gforge.<replaceable>company.com</replaceable>
801 # You may want to add these files to logrotate, or just use cronolog as shown below
802 CustomLog "<replaceable>/var/log/gforge</replaceable>/projects/access.log" combined
803 ErrorLog "<replaceable>/var/log/gforge</replaceable>/projects/error.log"
805 # CustomLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/projects/%Y/%m/%d/access.log" combined
806 # ErrorLog "|/usr/bin/cronolog <replaceable>/var/log/gforge</replaceable>/projects/%Y/%m/%d/error.log"
808 DocumentRoot <replaceable>/var/www/homedirs</replaceable>/groups
809 VirtualDocumentRoot <replaceable>/var/www/homedirs</replaceable>/groups/%1/htdocs
810 <Directory <replaceable>/var/www/homedirs</replaceable>/groups>
813 # WARNING - turning on php will allow any user
814 # to upload a php file to your server, and include
815 # the gforge local.inc file and get your password to
816 # connect to the database and have total control.
823 DirectoryIndex index.html index.htm
827 <para><filename>cronjobs/cvs-cron/usergroup.php</filename> copies from <filename>cronjobs/cvs-cron/default_page.php</filename> to <filename><replaceable>/var/www/homedirs</replaceable>/groups/<replaceable>projectname</replaceable>/htdocs/index.php</filename> but the above configuration disables PHP.</para>
832 <title>Full Text Indexing</title>
833 <para>If you want to enable full text indexing, follow these steps:</para>
836 <para>Find <filename>tsearch2.sql</filename> in your distribution of PostgreSQL and run it:</para>
838 # <userinput>su - postgres</userinput>
839 $ <userinput>psql -f <replaceable>/path/to/</replaceable>tsearch2.sql gforge</userinput>
841 <para>Since <literal>gforge</literal> PostgreSQL user is not superuser, access to some Tsearch2 tables should be additionally granted:</para>
843 # <userinput>su - postgres</userinput>
844 $ <userinput>psql gforge</userinput>
845 gforge=# <userinput>GRANT SELECT ON pg_ts_dict TO gforge;</userinput>
846 gforge=# <userinput>GRANT SELECT ON pg_ts_parser TO gforge;</userinput>
847 gforge=# <userinput>GRANT SELECT ON pg_ts_cfg TO gforge;</userinput>
848 gforge=# <userinput>GRANT SELECT ON pg_ts_cfgmap TO gforge;</userinput>
852 <para>Import data definitions:</para>
854 $ <userinput>cd <replaceable>/var/www/gforge</replaceable>/db</userinput>
855 $ <userinput>psql -U gforge -W -h localhost -f FTI.sql gforge</userinput>
856 $ <userinput>psql -U gforge -W -h localhost -f FTI-20050315.sql gforge</userinput>
857 $ <userinput>psql -U gforge -W -h localhost -f FTI-20050401.sql gforge</userinput>
858 $ <userinput>psql -U gforge -W -h localhost -f FTI-20050530.sql gforge</userinput>
862 <para>Enable Full Text Indexing by setting <varname>$sys_use_fti</varname> in FusionForge Configuration File <filename>local.inc</filename>.</para>
867 <title>JPGraph (Gantt Charting and Graphing Support)</title>
868 <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>
869 <para>Manual installation can be done like this:</para>
871 # tar -xzf jpgraph-1.19.tar.gz
872 # mkdir <replaceable>/var/www</replaceable>/jpgraph
873 # cp -R jpgraph-1.19/src/* <replaceable>/var/www</replaceable>/jpgraph
876 <para>If you want FHS-compliance, <filename class="directory">/usr/local/share/jpgraph</filename></para>
878 <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>
880 DEFINE("USE_CACHE", false);
883 <para>Be careful with JPGraph license: versions > 1.5.2 are not free (as in free speech). You must check license before use.</para>
888 <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>
889 <para>You'll also need to install <filename>utils/include.pl</filename> to <filename class="directory">/usr/share/gforge/lib/</filename>.</para>
892 <title>Jabber Support</title>
893 <para>FusionForge 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>
894 <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>
897 <title>Peer Ratings</title>
898 <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>
899 <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>
904 <title>Plugins</title>
906 <para>Since GForge 4.0, plugins are necessary as source code management is now provided by plugins (SCM* plugins).</para>
908 <para>For each plugin, you can find an <filename>INSTALL</filename> file in the plugin tarball.</para>
912 <title>Overview</title>
913 <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>
916 <title>Cronjobs</title>
917 <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>
920 <para><filename>usergroup.php</filename> creates user and groups in <filename>/etc/passwd</filename>, <filename>/etc/shadow</filename>, and <filename>/etc/group</filename>.</para>
923 <para><filename>cvs.php</filename> creates repositories.</para>
926 <para><filename>ssh_create.php</filename> copies SSH keys to user directories.</para>
929 <para><filename>history_parse.php</filename> collects statistics.</para>
932 <para>There are other cronjobs that can be activated too:</para>
935 <para><filename>plugins/scmcvs/cronjobs/tarballs.php</filename> creates tarballs</para>
938 <para><filename>plugins/scmcvs/bin/snapshots.sh</filename> creates tarballs. <varname>CVSROOT</varname> and <varname>SCMSNAPSHOTSDIR</varname> variables are hard-coded in the script, so you'll have to edit the script if necessary.</para>
941 <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>
942 <para>If you are using CVS 1.12, replace <filename>syncmail</filename> with updated version.</para>
944 # <userinput>cd <replaceable>/var/www/gforge</replaceable></userinput>
945 # <userinput>cp plugins/scmcvs/bin/syncmail-cvs-1.12 cronjobs/cvs-cron/syncmail</userinput>
947 <para>Replace <literal>%1{sVv}</literal> in <filename><replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/cvs.php</filename> with <literal>%p %{sVv}</literal>. Search for <literal>LockDir=</literal> in <filename>cronjobs/cvs-cron/cvscreate.sh</filename> and add the following line after it:</para>
949 echo "UseNewInfoFmtStrings=yes" >> $repositorypath/CVSROOT/config
953 <title>Installation</title>
955 <para>This guide doesn't cover chrooted CVS repositories which are always recommended.</para>
959 <para>Create default location for CVS repositories (<varname>$cvsdir_prefix</varname> in FusionForge configuration file):</para>
961 # <userinput>mkdir <replaceable>/cvsroot</replaceable></userinput>
965 <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>
967 # <userinput>mkdir <replaceable>/var/www/cvs</replaceable></userinput>
968 # <userinput>cp <replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/www/* <replaceable>/var/www/cvs</replaceable></userinput>
972 <para>Copy the scmcvs plugin config to <filename class="directory">/etc/gforge</filename>:</para>
974 # <userinput>cp -R <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/etc/* /etc/gforge</userinput>
978 <para>Make sure the cvs crons are executable:</para>
980 # <userinput>cd <replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/</userinput>
981 # <userinput>chmod 755 *.php *.sh</userinput>
985 <para>Copy CVS restricted shell:</para>
987 # <userinput>cp <replaceable>/var/www/gforge</replaceable>/cronjobs/cvs-cron/cvssh.pl /bin</userinput>
991 <para>Edit FusionForge 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>
994 <para>You may have to edit <filename>/etc/gforge/plugins/scmcvs/cvsweb.conf</filename> to change the cvsroot location:</para>
996 'gforge' => ['FusionForge-CVS', '<replaceable>/cvsroot/</replaceable>'],
1000 <para>Install the following non-core Perl modules:</para>
1003 <para>IPC::Run</para>
1006 <para>URI::Escape</para>
1011 <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>
1016 <para>Add entry for pserver in <filename>/etc/inetd.conf</filename>:</para>
1017 <para><literal>cvspserver stream tcp nowait root <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/bin/cvs-pserver cvs-pserver</literal></para>
1018 <para>Make sure that the wrapper script is executable:</para>
1020 # <userinput>chmod +x <replaceable>/var/www/gforge</replaceable>/plugins/scmcvs/bin/cvs-pserver</userinput>
1022 <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>
1024 <para>CVS pserver has long history of vulnerabilities and its use is highly discouraged.</para>
1031 <title>CVSTracker</title>
1033 <title>Overview</title>
1034 <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>
1035 <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>
1036 <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>
1039 <title>Installation</title>
1041 # <userinput>cd <replaceable>/var/www/gforge</replaceable>/plugins/cvstracker/</userinput>
1042 # <userinput>cp -R etc/plugins/cvstracker/ /etc/gforge/plugins/</userinput>
1044 <para>Edit <filename>/etc/gforge/plugins/cvstracker/config.php</filename> and change parameters.</para>
1045 <para>Uncomment <filename>update_loginfo.php</filename> in crontab.</para>
1047 <para>CVS Tracker is not enabled by default for project. You'll have to manually enable it.</para>
1054 <title>Overview</title>
1055 <para>SVN is also managed via plugin. The scmsvn plugin is included and activated by default in FusionForge. 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>
1056 <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>
1057 <para>Configuring svnserv for svn-over-ssh:
1060 <para><ulink url="http://svnbook.red-bean.com/en/1.0/ch06s03.html"/></para>
1063 <para><ulink url="http://www.logemann.org/day/archives/000099.html"/></para>
1066 <para><ulink url="http://bitworking.org/news/Getting_subversion_svn_ssh____to_work_with_PuTTY"/></para>
1072 <title>Installation</title>
1074 <para><emphasis>Instructions here are far from complete.</emphasis></para>
1077 #Create default location for SVN repositories
1080 # Optional - Set up some basic files for SVN-over-DAV only
1082 cp <replaceable>/var/www/gforge</replaceable>/cronjobs/dav-svn/www/* /var/www/svn/
1084 #copy the scmsvn config files to /etc/gforge/
1085 cp -R gforge/plugins/scmsvn/etc/plugins/scmsvn/ /etc/gforge/plugins/
1091 <title>Upgrading Existing Install</title>
1092 <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>
1093 <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>
1095 <para>You have to apply database schema changes and to run migration scripts in the right order.</para>
1099 <title>Most Common Problems</title>
1100 <para>Q: I get a blank page when I visit http://gforge.company.com/</para>
1101 <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>
1102 <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>
1104 $conn = @pg_connect(
1106 <para>So that it looks like:</para>
1110 <para>This will let debug output dump to the screen and may let you find the problem. Search the forums for more solutions.</para>
1111 <para>Q: <quote>Error Occurred In the Logger</quote> or other database permission problems</para>
1112 <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>
1113 <para>Q: Reporting or time tracking doesn't work</para>
1114 <para>A: Go to the reporting tab and scroll down so you can choose <quote>Initialize/Rebuild Reporting Tables</quote></para>
1115 <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>
1116 <para>Q: How do I upgrade my database?</para>
1117 <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>
1118 <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>
1119 <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>
1120 <para>Q: How do I backup FusionForge?</para>
1121 <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>
1122 <para>Q: Any time i enter an apostrophe in a text box, i get a parse error</para>
1123 <para>A: As stated in the instructions above, you should have <literal>magic_quotes_gpc=Off</literal> in your <filename>php.ini</filename> file.</para>
1124 <para>Q: Large uploads into FRS or the doc manager fail.</para>
1125 <para>A: Apache and the <filename>php.ini</filename> file need to have upload limits and possibly memory limits increased.</para>
1126 <para>Q: When I click on <filename>/projects/</filename> or <filename>/users/</filename> links, I get a <computeroutput>Page Not Found</computeroutput> error instead of the page I expected.</para>
1127 <para>A: Switch to/from the <Files projects> from/to the <Location /projects> directives in your <filename>httpd.conf</filename>. (Q&A provided by David Morsberger)</para>
projects / fusionforge / fusionforge.git / blob