Using in Production

Virtual Bugzilla server is a quick way to get your own Bugzilla running. However, it needs to be properly configured and secured to be used as a production bug tracker.

The following is the minimal list of tasks that should be done before virtual Bugzilla server is put to production mode:

• Change default passwords for: unix accounts (root/root, bugzilla/bugzilla), mysql database (root/root), bugzilla accounts (admin/admin);
• Close MySQL socket for public;
• Increase the amount of memory for the virtual machine to at least 192 MB;
• Change ethernet connection type from NAT to Bridged to make Bugzilla visible to other computers on your network;
• Assign a permanent IP address to the VM and bind it to a convenient hostname;
• Configure mail transfer agent (exim4) appropriately to your local network;
• Prepare a backup plan. (It's easy with VMWare - you can periodically make a copy of the whole VM.)

These tasks require Linux system administration skills and access to your local network configuration. Consult with your system administrator.

If you'd like to get commercial support from ALM Works in preparing a production Bugzilla server, please contact us.