Upgrading Team Edition¶
You can see a full list of install commands by running the following command:
Anaconda Team Edition 6.1.4 supports the ability to upgrade from the previous version while keeping the product operating.
You’ll see this feature in the list as
--upgrade-from PREVIOUS_DIR, where
PREVIOUS_DIR represents the location of the previous installation (where the
docker-compose.yml is located).
Extract the installer
First, extract the installer:
./ate-installer-6.1.4-<HASH>.sh -- --help`
You will see the folder
<HASH> represents your hash.
cd into the folder:
# Replace <HASH> with your hash cd ./ate-installer-6.1.4-<HASH>
From here, you can run the upgrade.
Default upgrade command
The following is the default command for upgrading to 6.1.4, meaning you may need to add more to the command depending on your
setup. This could mean appending more directives to your upgrade command, such as those in the following subsections. Run
./install.sh --help to see other options.
# Replace <FQDN> with your fully qualified domain name # Replace <PREVIOUS_DIR> with the location of the previous installation (where the docker-compose.yml is located) ./install.sh -d <FQDN> --upgrade-from <PREVIOUS_DIR>
For example, say your domain name is team-edition.example.com, and the previous installer is stored in /home/user/installers/ate-installer-6.1.3-xxx, then the proper command would be the following:
./install.sh -d team-edition.example.com --upgrade-from /home/user/installers/ate-installer-6.1.3-xxx
If your previous setup was for HTTPS, you’ll need to provide the TLS certificate and key:
# Replace <PREV_BASE_DIR> with the base directory where config and file storage are saved. The default value is /opt/anaconda/repo. # Replace <FQDN> with your fully qualified domain name # Replace <TLS_CERTIFICATE> and <TLS_KEY> with your TLS cert and key # Replace <PREVIOUS_DIR> with the location of the previous installation (where the docker-compose.yml is located) ./install.sh -b <PREV_BASE_DIR> -d <FQDN> --tls-cert <TLS_CERTIFICATE> --tls-key <TLS_KEY> --upgrade-from <PREVIOUS_DIR>
Custom implementation considerations
If you’re using a custom implementation, verify your
repo.conf (nginx configuration)
files reflect the upgraded changes.
Follow these steps to upgrade your version of Anaconda Team Edition from 6.1.0 or 6.1.1 to 6.1.3:
Upgrading does not require hardware upgrades. Your data integrity will not be impacted.
REPO_KEYCLOAK_SYNC_CLIENT_SECRETvalues from the
.envfile in the installer directory for your current version of Team Edition.
docker-compose stopin your current version’s install directory (most likely in the same location as your
docker-compose.ymlfile). This will stop the container(s) and preserve the data.
Download, extract, and install the new version of Team Edition using the 6.1.3 installer.
.envfile in the new version’s directory and replace
REPO_KEYCLOAK_SYNC_CLIENT_SECRETwith the values from the old install directory.
docker-compose up -d repo_apiin the new install directory.
Re-upload the license:
Via UI: Sign in as an admin and enter your license key via the following path: