1 Installation of FusionForge is a non-trivial undertaking, since it integrates
2 with so many different components across your system. A skilled sysadmin
3 is required to pull it off, or at the least a great deal of patience.
5 The result of a complete installation means automatic creation of CVS
6 and Subversion repositories, and having access to them controlled by
7 FusionForge and stats gathered from them. ViewCVS (used for CVS and
8 Subversion browsing) are two additional integration points.
10 BASICS OF INSTALLATION
11 ----------------------
14 For Ubuntu/Debian system, you should use the debian packaging, see
15 the fusionforge.org website for the correct instructions.
17 For an installation on CentOS or Red Hat, use the following command.
19 install.sh <hostname with domain>
21 That will install the bulk of the system and even set up a site admin
26 The information below may not be necessary if you succeeded installing
27 using the above method. However this info may give you an overview
28 of how the installation is done.
37 FusionForge has a lot of different pieces touching a lot of different components
38 in the system. Cronjobs are required to maintain the system, touching lots
39 of files on a daily and hourly basis, including /etc/* system files.
41 The plugins that now manage the CVS and SVN functionality have made
42 installation slightly harder because even more files have to be moved into
43 place during installation.
45 The manual installation of fusionforge is documented below. Be sure to follow
46 each step carefully, check the forums for frequently asked questions,
47 and ask your Apache, mailman, and postgresql installation questions in the
48 corresponding mailing lists rather than on the gforge forums where little
54 CVS is now managed via the scmcvs plugin which is included in the
55 plugins/ directory in the tarball downloaded from gforge.org. Most
56 of the files in scmcvs are intended for auto-installation on debian
57 systems and DO NOT APPLY to the majority of users. The scmcvs plugin
58 is activated by default in the gforge.sql database.
60 Cronjobs for CVS are included in cronjobs/crontab.in, but are commented
61 out by default for your security. cronjobs/cvs-cron/* contains the files
62 that are executed hourly to build permissions and create blank cvs trees.
63 Make sure these files are executed as root, and have proper execution bits
64 set. Each of these cronjobs has configuration parameters which you may
65 have to edit manually the paths in those files for your specific system.
71 If you want to use GForge's svn-over-DAV support and apache2 are
74 SVN is also managed via plugin - the scmsvn plugin is included and
75 activated by default in gforge.
77 The sample etc/gforge-httpd.conf.example file in this tarball contains
78 a COMPLETE AND WORKING vhost for subversion-over-dav. The gforge-install.sh
79 script will copy this to /etc/gforge/httpd.conf You may have to
80 alter the passwords and any other config options, but the sample config
81 shown has been used in dozens or even hundreds of installs and DOES WORK.
86 The cvstracker plugin allows for some integration between CVS
87 commits and the bug tracker and task manager. So, for example,
88 when you commit, you can reference bug and task IDs in your
89 commit message and have the commit linked to the corresponding
92 This works by having a script in the cvs server issue a POST
93 to the main website ( /plugins/cvstracker/newcommit.php )
95 See the plugins/cvstracker/README file for details. This
96 plugin is enabled by default in the gforge.sql database file.
97 As with the other plugins, you may manually place the config
98 files in /etc/gforge/plugins/cvstracker/ and uncomment the
99 cronjob in crontab.in.
104 The cronjobs require the PHP CGI to be installed and the php.ini
105 file to be properly configured with your include_path OR edit the
106 crontab.in file to set your include path.
108 In addition, you may have to symlink /usr/bin/php to /usr/bin/php4,
109 which is where the cronjobs expect your PHP CGI to be located.
115 Mailman is needed to create and use mailing lists with gforge.
116 Mailman is frequently installed in /var/mailman/ and the sample
117 vhost shown below will work with this setup without any changes.
119 Cronjobs for mailman are located in cronjobs/mail/*
121 cronjobs/mail/mailing_lists_create.php is used obviously to
122 create new mailing lists. You may have to edit /etc/gforge/local.inc
123 to change the location of the mailman bin/ directory.
125 For all problems with mailman installation and use, contact
126 the mailman mailing lists for help.
129 UPGRADING DATABASE - EXISTING INSTALL
130 -------------------------------------
132 To migrate to a newer version of GForge, you must import
133 your old database, FRS files, mailing lists, cvs and svn trees
134 into your new installation.
136 1) Completely install your new system
137 2) Move the mentioned files into place
138 3) Import your old database
139 4) go into the gforge/db directory and choose 'startpoint.php 4.0.2'
140 as the starting point of the installation (4.0.2 is an example)
141 5) ./upgrade-db.php - this script will run the updates in order.
142 If any of them fail, it will prompt you to continue. Generally,
143 you should always continue. Most are minor or informational errors.
146 WEB SETUP - MANUAL INSTALLATION
147 -------------------------------
149 The following are sample commands commonly issued for a manual installation:
151 tar -xjf gforge-X.X.tar.bz2
155 # BEFORE RUNNING THIS, determine your apacheuser/group
156 # and pass it as an argument as shown below.
158 # Argument 1: the main hostname you want to use.
159 # Argument 2: the apache user
160 # Argument 3: the apache group
161 # Argument 3: the IP address that you are listening on
163 ./gforge-install.sh gforge.company.com apacheuser apachegroup
166 # jpgraph install - use the 1.9.1 version from gforge.org
169 tar -xzf jpgraph-1.9.1.tar.gz
170 mv jpgraph-1.9.1/src/* /opt/jpgraph/
172 #you will have to edit jpgraph.php to set USE_CACHE=false
173 vim /opt/jpgraph/jpgraph.php
175 Apache will need to have a line added to its httpd.conf:
177 Include /etc/gforge/httpd.conf
179 Restart apache when you are done editing the file so the
180 changes can be picked up.
186 You may also add the include_path to the php.ini, as it will be
187 necessary for your php cgi to run the cron jobs.
189 register_globals = Off
190 magic_quotes_gpc = Off
192 include_path = ".:/opt/gforge/gforge/:/opt/gforge/gforge/www/include/:/etc/gforge/"
194 PHP CLI that is used by crontab.in may use different php.ini. Find
195 it by running the following command and add the above include_path
198 $ /usr/bin/php -i | fgrep php.ini
201 FRS - File Release System
202 -------------------------
204 FRS has been radically simplified. Simply create a directory and make
205 it owned by the webserver-user. Usually "chown -R apache:apache mydir"
208 This directory will be referenced in the GForge Config File as $sys_upload_dir
214 Edit the /etc/gforge/local.inc and set any specific variables
215 like sys_default_domain and any paths to files that are not right
221 Site admins are anyone who is an admin of group_id=1
223 To give the first user "Site Admin" privileges, register a new user,
224 and confirm it via the email link. Then enter the postgres command
225 line and issue these commands:
227 [gforge]# psql gforge
229 psql> SELECT user_id FROM users WHERE user_name='******MY NEW USERNAME*********';
231 The result of that query will be put into this next query:
233 psql> insert into user_group (user_id,group_id,admin_flags) values (*****YOUR NEW NUMERIC USER ID*****,1,'A');
239 This alias was already added by the gforge-install script:
247 Add yourself, and any others you wish, to the "Peer Ratings" project,
248 which should be at /projects/peerrating/ on the website. Make yourself
249 an "admin" of the project, and then proceed to "rate" other users on
252 Members of the "Peer Ratings" project, who are "admins" of the project
253 become the first trusted users. This is the only way to prime the pump
254 for the peer ratings system.
260 Cron jobs are in the cronjobs/ directory and the README file contains
261 a sample crontab. This gives you the basic cronjobs for updating
262 certain statistics and data on the site.
264 /cronjobs/cvs-cron/ contains scripts useful for creating blank cvs
265 trees and managing the /etc/groups /etc/passwd and /etc/shadow files.
266 See /cronjobs/README.root for more info.
268 /cronjobs/mail/ contains files useful for the creation of new mailing
269 lists in mailman and creating the /etc/aliases file.
271 **************************************************************************
272 WARNING!!! the following command will blow away any existing root crontab.
273 **************************************************************************
275 [root]# crontab cronjobs/crontab.in
277 Now edit the paths to the cron scripts:
281 IMPORTANT!!!! - the cvs-cron/usergroup.php cron script will meddle
282 with your /etc/passwd, /etc/group, and /etc/shadow files. By default,
283 this cron will save these files with a .new extension. You will have
284 to edit the cron script to remove the .new extension, but you must
285 make sure that it is properly generating your files or your server
288 Once you have manually run the usergroup.php file, look at the
289 /etc/*.new files and verify that they contain sensisble information.
290 When you are confident they are right, you can edit usergroup.php
291 to remove the .new extension and uncomment the cronjobs.
297 The installation was shown above. Be sure to use the 1.9.1 version
298 from gforge.org and set USE_CACHE=false as shown here.
300 DEFINE("USE_CACHE",false);
306 Q: I get a blank page when I visit http://gforge.company.com/
308 A: Most often you are missing the php-pgsql library that lets PHP
309 talk to the postgres database. Find a php-pgsql RPM or recompile
310 php to have pgql support.
312 If you're sure you have php-pgsql support, you can edit
313 common/include/database.php and remove the @ symbol from
318 So that it looks like:
322 This will let debug output dump to the screen and may let you find
323 the problem. Search the forums for more solutions.
326 Q: "Error Occurred In the Logger" or other database permission problems
328 A: As stated in the installation instructions, the database must be created,
329 owned, and accessed by the gforge user. This user is the only one who will
330 have total acess to all the tables. Any other user would have to be specifically
331 granted permissions with the GRANT commands in postgres.
334 Q: Reporting or time tracking doesn't work
336 A: Go to the reporting tab and scroll down so you can choose
337 "Initialize/Rebuild Reporting Tables"
339 You may also be missing GD support or be missing JPGraph or have it installed
340 improperly. The jpgraph/src/ directory should be specified accurately in your
341 local.inc file, and you should include a / at the end of the path specified.
342 In addition, you should modify jpgraph.php to set USE_CACHE=false
345 Q: How do I upgrade my database?
347 A: As stated above, you must apply the changes that are listed in date order
348 in the db/ directory to your database. Only the changes that are not already
349 in your old db/ directory should be applied, and they should be applied and
353 Q: I'm getting an error about BaseLanguage.class not being found.
355 A: Make sure your localization path is correctly specified in the local.inc
356 file and that it is readable AND writable by the apache user.
359 Q: When I click on "/projects/" or "/users/" links, I get the source code
360 instead of the page I expected.
362 A: As shown in the example httpd.conf files above, you may have to switch
363 to using the <Files> or <Location> directives depending on your server
367 Q: How do I backup GForge?
369 A: The only proper way to backup the gforge database is with pg_dump.
370 Any attempt to backup the filesystem while pgsql is running will result
371 in a useless and corrupt backup. You can backup CVS trees using tar as
372 long as they are not actively and heavily used during the backup.
373 Mailman and the FRS uploads dir can also be backed up with tar.
376 Q: Large uploads into FRS or the doc manager fail.
378 A: Apache and the php.ini file need to have upload limits and possibly
379 memory limits increased.