Instructions for upgrading from Early Access to the 1.0 release of Mingle

Before you get started, a couple of important points:

• We strongly recommend that you make a backup of the Mingle data directory and your database before starting the upgrade process.

• ANY TEMPLATES THAT WERE INSTALLED WITH THE EA RELEASE WILL BE REPLACED. This has no impact on any of your existing projects or any templates that you have created yourself. If you have modified the pre-installed templates and wish to keep them you must export them and then import them using a different name before the upgrade.

• At this point, Mingle project export files (’.mingle files’) created by an Early Access (EA) build cannot be imported into the 1.0 Mingle release. This only impacts project export files. The Mingle database can be upgraded and any projects in your EA database will be upgraded and fully usable as soon as you start a newly installed 1.0 Mingle server.

Windows
——-
1. Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\<login>\Mingle) and the port is 8080.

2. Run the Mingle uninstaller to remove your current installation. The uninstaller will stop the Mingle service if it is currently running.

3. Run the new installer, specifying the same data directory and port as the previous installer. The installer will automatically start the new Mingle service when it completes.

4. Open your browser to any Mingle page. You will be walked through the upgrade steps, including a database upgrade and accepting the ThoughtWorks End User License Agreement. All existing project data will be upgraded for continued use.

OS X
—
1. Note the location of the Mingle data directory and the port on which Mingle is currently running. These are both visible from the Mingle launcher application window.

2. Stop Mingle and quit the Mingle launcher application.

3. Drag the new copy of the Mingle application (Mingle.app) into your Applications directory (overwriting the old Mingle).

4. Start Mingle, specifying the same data directory and port as before.

5. Open your browser to any Mingle page. You will be walked through the upgrade steps, including a database upgrade and accepting the ThoughtWorks End User License Agreement. All existing project data will be upgraded for continued use.

Linux/Unix
—-—-
1. Note the location of the Mingle data directory and the port on which Mingle is currently running. These are contained in the mingle.properties file in the ‘mingle’ application directory.

2. If the Mingle server is currently running, stop it using the ’./MingleServer stop’ command inside the ‘mingle’ application directory.

3. Ensure that your Mingle data directory (specified in mingle.properties) is not inside the ‘mingle’ application directory. We strongly recommend that you do not place your data directory inside the ‘mingle’ application directory. This makes upgrades significantly more complicated. If your data directory is not inside the ‘mingle’ application directory skip ahead to step 4. IF YOUR DATA DIRECTORY IS INSIDE THE ‘MINGLE’ APPLICATION DIRECTORY, PLEASE FOLLOW THESE STEPS TO EXTRACT YOUR DATA:

• create a new data directory (we’ll use /var/mingle for this example)
• from inside the ‘mingle’ application directory…
• cp -R config /var/mingle
• cp -R public/attachments /var/mingle/public/attachments
• cp -R public/project /var/mingle/public/project

5. Untar the newly downloaded archive

6. Update the mingle.properties file in the new ‘mingle’ application directory to point to the previous data directory and port. (If you’ve backed up the old ‘mingle’ application directory, you can simply copy the file.)

7. Start Mingle, using ’./MingleServer start’ inside the new ‘mingle’ application directory.

8. Open your browser to any Mingle page. You will be walked through the upgrade steps, including a database upgrade and accepting the ThoughtWorks End User License Agreement. All existing project data will be upgraded for continued use.