Alternative Upgrade Option

This option installs a new instance of RhodeCode Enterprise and the ports a previous setup into the new instance.

If want to install a clean version of RhodeCode Enterprise, and then port the details of your previous instance into the new setup, use the following instructions.

Identify your production.ini

The two components you need for porting an older version into RhodeCode Enterprise are the production.ini file, and your RhodeCode Enterprise database. The production.ini file should already be pointing to your database. This file contains all the details of your setup. These are the details you will need to configure a new installation to work like a previous one.

The default location for older RhodeCode Enterprise versions is /home/user/rhodecode/data/production.ini

Configure the rhodecode.ini

The rhodecode.ini file is the equivalent configuration file for newer versions, RhodeCode Enterprise 3.0 and above. To configure this file with your old settings, use the following steps.

Note

Do not copy/paste the entire production.ini file and over-write the new rhodecode.ini as the newer file contains additional configuration settings.

  1. Open the /home/user/.rccontrol/instance-id/rhodecode.ini file and configure it with the following settings from your old production.ini file.
  2. Change the UUID of your new installation so that it matches your older version.
# Change this setting to match your old instance ID
## change this to unique ID for security
app_instance_uuid = d152ec7bf5ee4851a6dfca654783e772
  1. Set the database connection string to point to your database
#########################################################
### DB CONFIGS - EACH DB WILL HAVE IT'S OWN CONFIG    ###
#########################################################
sqlalchemy.db1.url = sqlite:////home/user/.rccontrol/instance-id/rhodecode.db

# Do not use localhost with MySQL DBs
sqlalchemy.db1.url = mysql://root:qweqwe@127.0.0.1/rhodecode
  1. Make further changes to the rhodecode.ini file if needed, for example email setup, or Celery configuration. For more information, see Post Installation Tasks.
  2. Upgrade your database settings so that they match the RhodeCode Enterprise 3.0 database setup. Use the following command:
# This makes minor changes to the database settings for older versions
# so that they behave as expected for 3.0
.rccontrol/enterprise-1/profile/bin/paster upgrade-db /path/to/ini_file --force-yes

Restart RhodeCode Enterprise

Restart the RhodeCode Enterprise instance so that it picks up the changes.

# Restart the instance you configured with changes
rccontrol restart enterprise-1

Post-update Tasks

  1. Once restarted, you will need to apply your new license token, see Licence Management.
  2. To make RhodeCode Enterprise pick up the repositories you imported, run remap and rescan.