6 Want to know what the status of this package is? Read
7 /usr/share/doc/@PACKAGE@/TODO.Debian or (even better)
8 <https://fusionforge.org/mediawiki/index.php/Roadmap>. If you miss a
9 feature, or find a bug, or want to help, don't hesitate to contact me
10 (Roland Mas <lolando@debian.org>) . Plenty of features are missing,
11 I'm working on some, but if you don't tell me which ones you miss the
12 most I might process them in the wrong order for you.
14 Please read the bug reports on the Debian bug-tracking system (at
15 <URL:http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=@PACKAGE@>)
16 before submitting new ones. Be warned that bug reports describing a
17 problem precisely and/or offering a solution will probably be
23 Although a few documentation files from upstream are included, they
24 are either very out of date or practically useless. I mostly include
25 them for completeness's sake (and per request, too). The files I'm
26 referring to are Install_Guide.html, Adminstration_Guide.html,
27 Contributor_Guide.html, INSTALL, and AUTHORS.
32 @FORGENAME@ is a big piece of software. It's far-reaching. It
33 fiddles with many different parts of the system. As automated as I
34 have tried to make its installation, there are still things that need
35 to be done by hand, maybe even by a system administrator.
37 First, you'll need a hostname. Get the @PACKAGE@.<your-domain>
38 DNS name to be created, pointing on the IP address of the host you're
39 installing @FORGENAME@ on. The "@PACKAGE@" part isn't required, you
40 can call it however you like. However, I'll assume you chose
41 "@PACKAGE@" from now on; substitute as needed.
43 If you want to use the Apache virtual hosting service, you'll even
44 need a delegation of a subdomain. Get your system administrator to
45 delegate you the SOA for the @PACKAGE@.<your-domain> subdomain.
46 This will allow @FORGENAME@ to create new hostnames for projects when
47 needed (foo.@PACKAGE@.<your-domain>, for instance), as well as some
48 hostnames needed by the system (for mailing-lists or SCM, for
51 The LDAP server is hosted on the same host and automatically
52 managed, therefore you should not have to worry too much about it.
53 You might be able to access it from another host, but I'm not sure
54 you'll be able to modify the entries in it. I would advise not to in
55 any case, since it would make the data contained in the LDAP directory
56 inconsistent with the real data stored in the PostgreSQL database.
58 You'll need a configured MTA for @FORGENAME@. Depending on whether
59 the @FORGENAME@ users are local or remote, you might need to set up a
60 smarthost or something else. @FORGENAME@ depends on a working mail
61 system, and you won't be able to create user accounts without it. I'm
62 not sure yet what advanced tricks need to be done with the MTA. There
63 might be some stuff to do with virtual domains for mailing-lists or
64 user email forwarding... I haven't fully investigated it yet. Your
65 contribution will be most welcome.
67 Depending on the targeted audience, you might want to get a real
68 SSL/TLS certificate from some certification authority, whether it be a
69 professional one or your personal one (or the one in your company).
70 Otherwise, just use mod-ssl-makecert as advised during the
71 configuration phase, and get your own custom certificate.
73 Do *not* delete the /etc/@PACKAGE@/*.template files. They are
74 needed. Do not alter them either unless you *know* what you're doing.
79 Once @FORGENAME@ is setup, it pretty much runs by itself. There
80 should be relatively few things to do for the administrator. The
81 following are random notes trying to document them.
83 You'll need to periodically check the Approve Pending Projects page
84 as well as the Approve News Bytes one, and take appropriate action.
85 That can be done by the `admin' user (or any user having admin
86 permissions on the `siteadmin' project) via the web interface.
88 If you need to add skills to the database after installation, you
89 can use the sf-add-skill script. Give it a skill (or a list of
90 skills) and it'll insert it into the databse. This script is located
91 in /usr/share/@PACKAGE@/bin/.
93 For cvs to work you have to add a symlink doing
94 ln -s /var/lib/@PACKAGE@/chroot/cvsroot /cvsroot.
95 We can't do this for Debian policy reason that forbid this.
97 ln -s /var/lib/@PACKAGE@/chroot/svnroot /svnroot is to be done
99 Don't forget about adding
100 SYSLOGD="-p /dev/log -a /var/lib/@PACKAGE@/chroot/dev/log" in /etc/default/syslog
101 This is a WARNING you might have seen at install, essential if you run
102 anonymous cvs in a root jail (This is the default in Debian)
104 If you would like to add a theme to your @FORGENAME@, you'll first
105 have to compose it. Please refer to README.Themes.
107 Other customisations are described in README.Custom.
112 Apart from the SourceForge crew at VA Linux, who did (and probably
113 still do) a great job with SF, I'd like to send my thanks to Guillaume
114 Morin, who wrote a very thorough SourceForge installation guide. That
115 guide gives step-by-step instructions for the installation procedure,
116 and a big part of the packaging task was to turn these instructions
117 into automated scripts. Even if this package has evolved a lot since
118 then, it was originally based on his guide.
120 Thanks also to all who tested packages and helped correct many
121 errors of mine. In particular, thanks to all who submitted patches.
123 And mega-thanks to Christian Bayle. That guy single-handedly
124 adapted and fixed all the scripts related to SCM, DNS, SSH accounts,
127 -- Roland Mas <lolando@debian.org>, Thu Jul 24 21:33:33 2003