> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrading Team Edition

* [Upgrading from 6.1.4 to 6.1.5](#upgrading-from-6-1-4-to-6-1-5)
* [Upgrading from 6.1.3 to 6.1.4](#upgrading-from-6-1-3-to-6-1-4)
* [Upgrading from 6.1.0/6.1.1 to 6.1.3](#upgrading-from-6-1-0/6-1-1-to-6-1-3)

## Upgrading from 6.1.4 to 6.1.5

### Install commands

You can see aa full list of install commands by running the following command:

```sh theme={null}
./install.sh --help
```

Anaconda Team Edition 6.1.5 supports the ability to upgrade from the previous version while keeping the product operating. You will 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).

### Upgrade steps

**Extract the installer**

First, extract the installer:

```sh theme={null}
./ate-installer-6.1.5-<HASH>.sh -- --help
```

You will see the folder `./ate-installer-6.1.5-<HASH>`, where `<HASH>` represents your **HASH**

cd into the folder:

```sh theme={null}
#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.5, meaning you might 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.

```sh theme={null}
# 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.4-xxx*,
then the proper command would be the following:

```sh theme={null}
./install.sh -d team-edition.example.com --upgrade-from /home/user/installers/ate-installer-6.1.4gi-xxx
```

**HTTPS setup**

If your previous setup was for HTTPS, you’ll need to provide the TLS certificate and key:

```sh theme={null}
# 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 `docker-compose.yml` and/or `repo.conf` (nginx configuration)
files reflect the upgraded changes.

## Upgrading from 6.1.3 to 6.1.4

### Install commands

You can see a full list of install commands by running the following command:

```sh theme={null}
./install.sh --help
```

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).

### Upgrade steps

**Extract the installer**

First, extract the installer:

```sh theme={null}
./ate-installer-6.1.4-<HASH>.sh -- --help
```

You will see the folder `./ate-installer-6.1.4-<HASH>`, where `<HASH>` represents your hash.

cd into the folder:

```sh theme={null}
# 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 might 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.

```sh theme={null}
# 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:

```sh theme={null}
./install.sh -d team-edition.example.com --upgrade-from /home/user/installers/ate-installer-6.1.3-xxx
```

**HTTPS setup**

If your previous setup was for HTTPS, you’ll need to provide the TLS certificate and key:

```sh theme={null}
# 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 `docker-compose.yml` and/or `repo.conf` (nginx configuration)
files reflect the upgraded changes.

## Upgrading from 6.1.0/6.1.1 to 6.1.3

Follow these steps to upgrade your version of Anaconda Team Edition from 6.1.0 or 6.1.1 to 6.1.3:

<Note>
  Upgrading does not require hardware upgrades. Your data integrity will not be impacted.
</Note>

1. Save the `REPO_TOKEN_CLIENT_SECRET` and `REPO_KEYCLOAK_SYNC_CLIENT_SECRET` values from the `.env` file in the installer directory for your current version of Anaconda Team Edition.
2. Run `docker-compose stop` in your current version’s install directory (most likely in the same location as your `docker-compose.yml` file). This will stop the container(s) and preserve the data.
3. Download, extract, and install the new version of Anaconda Team Edition using the 6.1.3 installer.
4. Modify the `.env` file in the new version’s directory and replace `REPO_TOKEN_CLIENT_SECRET` and `REPO_KEYCLOAK_SYNC_CLIENT_SECRET` with the values from the old install directory.
5. Run `docker-compose up -d repo_api` in the new install directory.
6. Re-upload the license:

   * Via UI: Sign in as an admin and enter your license key via the following path:

     ```sh theme={null}
     <DOMAIN>/enter-license-key
     ```

   * Via API:

     ```sh theme={null}
     POST /system/license
     ```