Skip to content

On-prem

This page describes the prerequisites for deploying Seqera Platform Enterprise to your on-premises infrastructure.

See Docker Compose for instructions to deploy via Docker Compose.

See Kubernetes for instructions to deploy via Kubernetes.

Prerequisites#

Ensure that you satisfy the requirements for your installation. Refer to this list of prerequisites:

  • SMTP server: An SMTP server is required to send emails from your Seqera instance.

    If you don't have your own mail server, you can use an external service from a cloud provider. Visit the provider's corresponding Prerequisites page for more information and consult your IT team to select the most suitable solution for your organization.

  • MySQL database: An external database (i.e., external to your Docker Compose or Kubernetes deployment) is highly recommended for production deployments. If you don't have your own database service, you can use an external service from a cloud provider. Visit the provider's corresponding Prerequisites page for more information and consult your IT team to select the most suitable solution for your organization.

    If you decide to use an external database, you must create a MySQL user and database manually. See Configuration for more details.

  • (Optional) SSL certificate: An SSL certificate is required for your Seqera instance to handle HTTPS traffic.

    From version 22.1.1, HTTP-only implementations must set the TOWER_ENABLE_UNSAFE_MODE=true environment variable in the Seqera hosting infrastructure to enable user login. HTTP must not be used in production environments.

Seqera container images#

Seqera Platform Enterprise is distributed as a collection of Docker containers available through the Seqera container registry cr.seqera.io. Contact support to get your container access credentials. Once you've received your credentials, retrieve the Seqera container images:

  1. Retrieve the username and password you received from Seqera support.

  2. Run the following Docker command to authenticate to the registry (using the username and password values copied in step 1):

    1
    docker login -u '<USERNAME>' -p '<PASSWORD>' cr.seqera.io

  3. Pull the Seqera container images with the following commands:

    1
2
3
    docker pull cr.seqera.io/private/nf-tower-enterprise/backend:v23.2.0

docker pull cr.seqera.io/private/nf-tower-enterprise/frontend:v23.2.0

cr.seqera.io is the default Seqera container image registry from version 22.4. Use of the AWS, Azure, and Google Cloud image registries in existing installations is still supported but is deprecated for new installations from June 2023.

Back to top