Skip to content

On-prem

This page describes the prerequisites for deploying Tower to your own (on-premises) infrastructure.

Tower container images#

You need to be able to pull the Tower container images from one of Seqera's container registries. Visit the corresponding Prerequsites page for instructions on how to acquire them:

Mandatory prerequisites#

SMTP server#

An SMTP server is required to send emails from Tower.

If you don't have your own mail server, you might be able to use an external service from one of the cloud providers. Visit the corresponding Prerequsites page for more information, and consult your IT team to see what works best 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 might be able to use an external service from one of the cloud providers. Visit the corresponding Prerequsites page for more information, and consult your IT team to see what works best for your organization.

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

Docker Compose#

A computer with Docker installed is required to deploy Tower via Docker Compose.

Kubernetes#

A Kubernetes cluster 1.19 or later is required to deploy Tower via Kubernetes.

Optional prerequisites#

SSL certificate#

Required to allow your Tower instance to handle HTTPS traffic.

Warning

Starting in Tower 22.1.1, HTTP-only implementations must set the following environment variable in their Tower hosting infrastructure in order for users to be able to successfully log in: TOWER_ENABLE_UNSAFE_MODE=true.

Back to top