Status
------
Want to know what the status of this package is? Read
-/usr/share/doc/gforge/TODO.Debian or (even better)
+/usr/share/doc/pkgname/TODO.Debian or (even better)
<http://savannah.gnu.org/support/?group_id=259>. If you miss a
feature, or find a bug, or want to help, don't hesitate to contact me
(Roland Mas <lolando@debian.org>) . Plenty of features are missing,
most I might process them in the wrong order for you.
Please read the bug reports on the Debian bug-tracking system (at
-<URL:http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gforge>)
+<URL:http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pkgname>)
before submitting new ones. Be warned that bug reports describing a
problem precisely and/or offering a solution will probably be
processed faster :-)
have tried to make its installation, there are still things that need
to be done by hand, maybe even by a system administrator.
- First, you'll need a hostname. Get the gforge.<your-domain>
+ First, you'll need a hostname. Get the pkgname.<your-domain>
DNS name to be created, pointing on the IP address of the host you're
-installing GForge on. The "gforge" part isn't required, you
+installing GForge on. The "pkgname" part isn't required, you
can call it however you like. However, I'll assume you chose
-"gforge" from now on; substitute as needed.
+"pkgname" from now on; substitute as needed.
If you want to use the Apache virtual hosting service, you'll even
need a delegation of a subdomain. Get your system administrator to
-delegate you the SOA for the gforge.<your-domain> subdomain.
+delegate you the SOA for the pkgname.<your-domain> subdomain.
This will allow GForge to create new hostnames for projects when
-needed (foo.gforge.<your-domain>, for instance), as well as some
+needed (foo.pkgname.<your-domain>, for instance), as well as some
hostnames needed by the system (for mailing-lists or SCM, for
instance).
Otherwise, just use mod-ssl-makecert as advised during the
configuration phase, and get your own custom certificate.
- Do *not* delete the /etc/gforge/*.template files. They are
+ Do *not* delete the /etc/pkgname/*.template files. They are
needed. Do not alter them either unless you *know* what you're doing.
If you need to add skills to the database after installation, you
can use the sf-add-skill script. Give it a skill (or a list of
skills) and it'll insert it into the databse. This script is located
-in /usr/share/gforge/bin/.
+in /usr/share/pkgname/bin/.
For cvs to work you have to add a symlink doing
-ln -s /var/lib/gforge/chroot/cvsroot /cvsroot.
+ln -s /var/lib/pkgname/chroot/cvsroot /cvsroot.
We can't do this for Debian policy reason that forbid this.
For svn similar
-ln -s /var/lib/gforge/chroot/svnroot /svnroot is to be done
+ln -s /var/lib/pkgname/chroot/svnroot /svnroot is to be done
Don't forget about adding
-SYSLOGD="-p /dev/log -a /var/lib/gforge/chroot/dev/log" in /etc/default/syslog
+SYSLOGD="-p /dev/log -a /var/lib/pkgname/chroot/dev/log" in /etc/default/syslog
This is a WARNING you might have seen at install, essential if you run
anonymous cvs in a root jail (This is the default in Debian)