Set up the initial data for CollabNet SourceForge Enterprise 5.0

CollabNet SourceForge Enterprise 5.0 needs some data to start up with. You can bring in the data from an existing SourceForge Enterprise instance, or create sample data to get a new site started.

1. If you are upgrading onto new hardware, stop the Apache web server and the database on the new machine.
   
   • /etc/init.d/httpd stop
   • /etc/init.d/postgresql stop
2. Move the web server data out of the way.
   • mkdir /var/www/html/sourceforge44
   • mv /var/www/html/{css,sf-help,sf-images} /var/www/html/sourceforge44
3. Ensure that the data from SourceForge 4.4 SP1 database and SCM component is available to your new installation.
   • If your data is mounted from a separate machine, remount it in the equivalent location on the new machine.
   • If your data is on the same machine as the application, use the export/import tools that come with the database and SCM tool you are using.
4. Restart the database for the new sit.
   • /etc/init.d/<postgresql | oracle> start
5. Bring back the file system data from the install directory that you moved out of the way.
   Tip: To save time, you may want to use a tar command like this:

   • cd /usr/local/sourceforge44/var
   • tar cf - . | (cd /usr/local/sourceforge/var ; tar xf -)
6. Use the migrate.py script to convert your site data.
   • /usr/local/sourceforge/runtime/scripts/migrate.py
   The migrate.py script locates the SourceForge 4.4 SP1 data according to the values in the site-options.conf file, and modifies the data to work with SourceForge 5.0.
   Note: This includes configuration data for LDAP and the James mail server. Any modifications that you have applied to these components on your SourceForge Enterprise Edition 4.4 site are reproduced on your CollabNet SourceForge Enterprise 5.0 site.
7. If this is a new installation, set up the initial data now.
   • cd <INSTALLATION_SOURCE>
   • ./bootstrap-data.sh -d <INSTALLATION_DIR> -n
   Note: If you are upgrading to CollabNet SourceForge 5.0 from CollabNet 4.4 SP1, skip this step.
8. If SELinux is running, modify it to allow the services SourceForge requires.
   1. Change the context for your local Subversion repository.
      • chcon -R -h -t httpd_sys_content_t /svnroot
   2. Change the context for your local CVS repository, if you have one.
      • chcon -R -h -t httpd_sys_content_t /cvsroot
   3. Change the context of the Subversion repository that handles the branding (look and feel) of your site.
      • chcon -R -h -t httpd_sys_content_t /sf-svnroot
      • chcon -R -h -t httpd_sys_content_t /usr/local/sourceforge/var/overrides