Frequently asked questions about CollabNet
TeamForge system administration
Use this background information to help you set up, maintain and upgrade a CollabNet
TeamForge
installation.
- What does it take to install CollabNet TeamForge ?
To install CollabNet TeamForge , you download the software, make decisions about how you want the site to work, and set up data for the site to work with.
- What does it mean to run CollabNet TeamForge on a virtual machine?
CollabNet TeamForge can run as a virtual machine image in a VMWare Player. You get all the functionality of CollabNet TeamForge with the ease of installation and maintenance that comes with VMWare.
- Why won't my CollabNet TeamForge virtual machine installation start?
CollabNet TeamForge won't start, or you receive an error message when trying to access your site.
- Why does my CollabNet TeamForge site show a different time than the host machine it is running on?
In some cases it is possible for the clock in the CollabNet TeamForge VMware image to drift from that of the host machine. If you notice this issue, you can set the CollabNet TeamForge VMware image to synchronize time with an external NTP server.
- How does Source Forge Enterprise Edition (SFEE) manage security?
SFEE is a secure, centralized, enterprise-grade solution for optimizing distributed development.
- What is a patch?
A patch is a package of code that fixes or adds to the functionality of a CollabNet product. Patches are also known as "component upgrades."
- Does CollabNet TeamForge support merge tracking?
The Subversion repositories that are installed with CollabNet TeamForge run on Subversion 1.5, which supports merge tracking.
- Should I move my TeamForge database to its own server?
If you expect your site to have heavy user traffic, you may want to run the site's database on its own server.
- Should I move my source control application to its own server?
If you anticipate heavy source code check-in and check-out traffic, consider setting up the source code application on its own server.