Help

Upgrading from Mingle 1.1

Before you get started

  • The upgrade to 2.0 involves migration of your existing data which is a very sensitive process. We strongly recommend that you make a backup of the mingle data directory and your database before starting the upgrade process. DO NOT SHUT DOWN THE SERVER IN THE MIDDLE OF THE UPGRADE PROCESS AT ANY COST.
  • ANY TEMPLATES THAT WERE INSTALLED WITH THE PREVIOUS RELEASES 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.
  • The mingle database will be upgraded and any projects in your 1.1 database will be upgraded and fully usable as soon as you start a newly installed 2.0 Mingle server.
  • Any old project export files (.mingle files) can be directly imported into the 2.0 version of the application. They will be automatically upgraded upon import.

These instructions are for upgrading from Mingle 1.1 to Mingle 2.0. Look here to see how to upgrade from Mingle 1.0. Upgrades from older versions, specifically, the 2.0 Early Access release and 1.0 Early Access release, are not supported.

Installing the software

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\[username]\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. 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. All existing project data will be upgraded for continued use.

Linux/Unix (except Solaris)

  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. Untar the newly downloaded archive.
  4. 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.)
  5. Start Mingle, using './MingleServer start' inside the new 'mingle' application directory.
  6. Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.

Solaris

The steps to install on Solaris are very similar to that on any other UNIX except

  • You would use the UNIX zip installer rather than the tar.gz installer due to the fact that the default Solaris tar command is incompatible with the format with GNU tar.
  • You will have to ensure that the MingleServer script in the application directory has execute permissions.

After installation is complete...

Numeric properties and precision

Mingle 2.0 introduces numeric property types. Some Mingle charts and tables will now only work with numeric properties. In order that your 1.1 charts and tables do not break the installation process converted any existing properties that contain all numbers to this new numeric property type.

Each project will have a numeric precision that can be managed on the project's main administration. After installation this precision will be set to 10. You may likely wish to lower this value to 2 or 3.

Transition and wiki page names

Mingle 2.0 fixes a couple of issues with the names of transitions and wiki pages. Prior to 2.0 it was possible to create transitions with names that only differed in case. That same was true with wiki pages. This is no longer possible in Mingle 2.0. If you had transitions or pages with such names, one of them will keep the original name, and all subsequence will be given unique suffixes. E.g., If you had 'dev_setup' and 'Dev_Setup' pages they would become 'dev_setup' and 'Dev_Setup_1'

Using LDAP for authentication

The authentication settings for Mingle are controlled through the [mingle_data_directory]/config/auth-config.yml file. This file is created by default on all brand new installations. These settings mostly pertain to LDAP integration. For a detailed explanation of what the various properties of this file represent, you can read the LDAP authentication README file included with this distribution. The location of this file varies by distribution.

On OSX
  1. Right click the Mingle application bundle and select 'Show package contents'
  2. Once the Finder window opens, navigate to Contents/Resources/app/plugins/ldap_auth
  3. The README file here contains details of how to configure the LDAP authentication plugin
On Unix
  1. Navigate to the unizipped/untarred folder that contains the MingleServer script.
  2. Under this directory, locate the plugins/ldap_auth directory
  3. The README file here contains details of how to configure the LDAP authentication plugin
On Windows
  1. Navigate to the directory where you installed the application (typically C:\Program Files\Mingle-2_0)
  2. Under this directory, locate the plugins/ldap_auth directory
  3. The README file here contains details of how to configure the LDAP authentication plugin

Setting password format restrictions

If you would like the password format for all your users to be a combination of numbers, letters and punctuation, and enforced strictly, set

password_format: :strict

The default, which is empty, places no restrictions on formats of the password.