On premise

We offer a self-hosted version of Tuist Cloud for organizations that require more control over their infrastructure. This version allows you to host Tuist Cloud on your own infrastructure, ensuring that your data remains secure and private.

If you signed an agreement with us to use Tuist Cloud on-premise, you can follow the instructions below to set up your environment.

Release cadence

Tuist Cloud is released every Monday and the version name follows the convention name {MAJOR}.YY.MM.DD. The date component is used to warn the CLI user if their hosted version is 60 days older than the release date of the CLI. It's crucial that on-premise organizations keep up with Tuist Cloud updates to ensure their developers benefit from the most recent improvements and that we can drop deprecated features with the confidence that we are not breaking any of the on-premise setups.

The major component of the CLI is used to flag breaking changes in Tuist Cloud that will require coordination with the on-premise users. You should not expect us to use it, and in case we needed, rest asure we'll work with you in making the transition smooth.

RELEASE NOTES

You'll be given access to a tuist/cloud-on-premise repository associated with the registry where images are published. Every new released will be published in that repository as a GitHub release and will contain release notes to inform you about what changes come with it.

Runtime requirements

This section outlines the requirements for hosting Tuist Cloud on your infrastructure.

Running Docker-virtualized images

We distribute Tuist Cloud as a Docker image via GitHub’s Container Registry.

To run it, your infrastructure must support running Docker images. Note that most infrastructure providers support it because it’s become the standard container for distributing and running software in production environments.

Postgres database

In addition to running the Docker images, you’ll need a Postgres database to store relational data. Most infrastructure providers include Posgres databases in their offering (e.g., AWS & Google Cloud).

MIGRATIONS

The Docker image's entrypoint automatically runs any pending schema migrations before starting the service.

Storage

You’ll also need a solution to store files (e.g. framework and library binaries). Currently we support any storage that's S3-compliant.

Configuration

The configuration of the service is done at runtime through environment variables. Given the sensitive nature of these variables, we advise encrypting and storing them in secure password management solutions. Rest assured, Tuist Cloud handles these variables with utmost care, ensuring they are never displayed in logs.

LAUNCH CHECKS

The necessary variables are verified at startup. If any are missing, the launch will fail and the error message will detail the absent variables.

License configuration

As an on-premise user, you'll receive a license key that you'll need to expose as an environment variable. This key is used to validate the license and ensure that the service is running within the terms of the agreement.

Environment variable	Description	Required	Default	Example
`TUIST_LICENSE`	The license provided after signing the service level agreement	Yes		`******`

EXPIRATION DATE

Licenses have an expiration date. Users will receive a warning while using Tuist commands that interact with Tuist Cloud if the license expires in less than 30 days. If you are interested in renewing your license, please reach out to [email protected].

Base environment configuration

Environment variable	Description	Required	Default	Example
`DATABASE_URL`	The URL to access the Postgres database. Note that the URL should contain the authentication information	Yes		`postgres://username:[email protected]/production`
`TUIST_USE_SSL_FOR_DATABASE`	When true, it uses SSL to connect to the database	No	`1`	`1`
`TUIST_APP_URL`	The base URL to access the instance from the Internet	Yes		https://cloud.tuist.io
`TUIST_SECRET_KEY_BASE`	The key to use to encrypt information (e.g. sessions in a cookie)	Yes
`TUIST_SECRET_KEY_PASSWORD`	Pepper to generate hashed passwords	No	`$TUIST_SECRET_KEY_BASE`
`TUIST_SECRET_KEY_TOKENS`	Secret key to generate random tokens	No	`$TUIST_SECRET_KEY_BASE`
`TUIST_USE_IPV6`	When `1` it configures the app to use IPv6 addresses	No	`0`	`1`

Authentication environment configuration

We facilitate authentication through identity providers (IdP). To utilize this, ensure all necessary environment variables for the chosen provider are present in the Tuist Cloud’s operating environment. Missing variables will result in Tuist Cloud bypassing that provider.

GitHub

We recommend authenticating using a GitHub App but you can also use the OAuth App. Make sure to include all essential environment variables specified by GitHub in the Tuist Cloud environment. Absent variables will cause Tuist Cloud to overlook the GitHub authentication. To properly set up the GitHub app:

In the GitHub app's general settings:
- Copy the Client ID and set it as TUIST_GITHUB_OAUTH_ID
- Create and copy a new client secret and set it as TUIST_GITHUB_OAUTH_SECRET
- Set the Callback URL as http://YOUR_APP_URL/users/auth/github/callback. YOUR_APP_URL can also be your server's IP address.
In the Permissions and events's Account permissions section, set the Email addresses permission to Read-only.

You'll then need to expose the following environment variables in the environment where Tuist Cloud runs:

Environment variable	Description	Required	Default	Example
`TUIST_GITHUB_OAUTH_ID`	The client ID of the application	Yes		`Iv1.a629723000043722`
`TUIST_GITHUB_OAUTH_SECRET`	The client secret of the application	Yes		`232f972951033b89799b0fd24566a04d83f44ccc`

Google

You can set up authentication with Google using OAuth 2. For that, you'll need to create a new credential of type OAuth client ID. When creating the credentials, select "Web Application" as application type, name it Tuist Cloud, and set the redirect URI to {base_url}/users/auth/google/callback where base_url is the URL your hosted-service is running at. Once you create the app, copy the client ID and secret and set them as environment variables GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET respectively.

CONSENT SCREEN SCOPES

You might need to create a consent screen. When you do so, make sure to add the userinfo.email and openid scopes and mark the app as internal.

Okta

You can enable authentication with Okta through the OAuth 2.0 protocol. You'll have to create an app on Okta with the following configuration:

App integration name: Tuist Cloud
Grant type: Enable Authorization Code for Client acting on behalf of a user
Sign-in redirect URL: {url}/users/auth/github/callback where url is the public URL your service is accessed through.
Assignments: This configuration will depend on your security team requirements.

If you'd like Tuist Cloud to detect when a user is removed from the application, you'll have to configure an event hook. In your Okta organization, go to Workflow > Event Hooks and create a new event hook with the following data:

Name: Notify memberhip removal to Tuist Cloud
URL: {url}/webhooks/okta where url is the public URL your service is accessed through.
Authentication field: Authorization
Authentication secret: A token that Tuist Cloud uses to validate the webhooks.
Subscribe to events Include User unassigned from app

Once the app is created you'll need to set the following environment variables:

Environment variable	Description	Required	Default	Example
`TUIST_OKTA_SITE`	The URL of your Okta organization	Yes		`https://your-org.okta.com`
`TUIST_OKTA_CLIENT_ID`	The client ID to authenticate against Okta	Yes
`TUIST_OKTA_CLIENT_SECRET`	The client secret to authenticate against Okta	Yes
`TUIST_OKTA_AUTHORIZE_URL`	The authorize URL	No	`{OKTA_SITE}/oauth2/<authorization_server>/v1/authorize`
`TUIST_OKTA_TOKEN_URL`	The token URL	No	`{OKTA_SITE}/oauth2/<authorization_server>/v1/token`
`TUIST_OKTA_USER_INFO_URL`	The token URL	No	`{OKTA_SITE}/oauth2/<authorization_server>/v1/userinfo`
`TUIST_OKTA_EVENT_HOOK_SECRET`	A secret to validat event hooks delivered by Okta	No

Storage environment configuration

Tuist Cloud needs storage to house artifacts uploaded through the API. It's essential to configure one of the supported storage solutions for Tuist Cloud to operate effectively.

S3-Compliant storages

Environment variable	Description	Required	Default	Example
`TUIST_S3_ACCESS_KEY_ID`	The access key identifier	Yes		`AKIAA2LQP3CCOZ6WT6CF`
`TUIST_S3_SECRET_ACCESS_KEY`	The access key secret	Yes		`A2dAWLnB4k3px9DVunCsnV1fap/zkTx8+lIVcqry`
`TUIST_S3_BUCKET_NAME`	Name of the bucket	Yes		`my-bucket`
`TUIST_S3_REGION`	The bucket's region	No	`eu-west-1`	`us-east-1`
`TUIST_S3_ENDPOINT`	Custom endpoint	No	`https://amazonaws.com`	`https://custom-domain.com`
`AWS_PROFILE`	Set an AWS profile for authorization. Doesn't work with other storages	No		`user1`

For Google Cloud Storage, follow these docs to get the TUIST_S3_ACCESS_KEY_ID and TUIST_S3_SECRET_ACCESS_KEY pair. The TUIST_S3_ENDPOINT should be set to https://storage.googleapis.com. Other environment variables are the same as for any other S3-compliant storage.

Deployment

On-premise users are granted access to the repository located at tuist/cloud-on-premise which has a linked container registry for pulling images. Currently, the container registry allows authentication only as an individual user. Therefore, users with repository access must generate a personal access token within the Tuist organization, ensuring they have the necessary permissions to read packages. After submission, we will promptly approve this token.

USER VS ORGANIZATION-SCOPED TOKENS

Using a personal access token presents a challenge because it's associated with an individual who might eventually depart from the enterprise organization. GitHub recognizes this limitation and is actively developing a solution to allow GitHub apps to authenticate with app-generated tokens.

Pulling the Docker image

After generating the token, you can retrieve the image by executing the following command:

bash

echo $TOKEN | docker login ghcr.io -u USERNAME --password-stdin
docker pull ghcr.io/tuist/cloud-on-premise:latest

Deploying the Docker image

The deployment process for the Docker image will differ based on your chosen cloud provider and your organization's continuous deployment approach. Since most cloud solutions and tools, like Kubernetes, utilize Docker images as fundamental units, the examples in this section should align well with your existing setup.

We recommend establishing a deployment pipeline that that runs every Tuesday, pulling and deploying fresh images. This ensures you consistently benefit from the latest improvements.

IMPORTANT

If your deployment pipeline needs to validate that the server is up and running, you can send a GET HTTP request to /ready and assert a 200 status code in the response.

Fly

To deploy the app on Fly, you'll require a fly.toml configuration file. Consider generating it dynamically within your Continuous Deployment (CD) pipeline. Below is a reference example for your use:

toml

app = "tuist-cloud"
primary_region = "fra"
kill_signal = "SIGINT"
kill_timeout = "5s"

[experimental]
  auto_rollback = true

[env]
  # Your environment configuration goes here
  # Or exposed through Fly secrets

[processes]
  app = "/usr/local/bin/hivemind /app/Procfile"

[[services]]
  protocol = "tcp"
  internal_port = 8080
  auto_stop_machines = false
  auto_start_machines = false
  processes = ["app"]
  http_options = { h2_backend = true }

  [[services.ports]]
    port = 80
    handlers = ["http"]
    force_https = true

  [[services.ports]]
    port = 443
    handlers = ["tls", "http"]
  [services.concurrency]
    type = "connections"
    hard_limit = 100
    soft_limit = 80

  [[services.http_checks]]
    interval = 10000
    grace_period = "10s"
    method = "get"
    path = "/ready"
    protocol = "http"
    timeout = 2000
    tls_skip_verify = false
    [services.http_checks.headers]

[[statics]]
  guest_path = "/app/public"
  url_prefix = "/"

Then you can run fly launch --local-only --no-deploy to launch the app. On subsequent deploys, instead of running fly launch --local-only, you will need to run fly deploy --local-only. Fly.io doesn't allow to pull private Docker images, which is why we need to use the --local-only flag.

Docker Compose

Below is an example of a docker-compose.yml file that you can use as a reference to deploy the service:

yaml

version: '3.8'
services:
  db:
    image: postgres:14.1-alpine
    restart: always
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
    ports:
      - '5432:5432'
    volumes: 
      - db:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 5s
      timeout: 5s
      retries: 5

  pgweb:
    container_name: pgweb  
    restart: always  
    image: sosedoff/pgweb
    ports:
      - "8081:8081"
    links:
      - db:db  
    environment:
      PGWEB_DATABASE_URL: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
    depends_on:
      - db 

  tuist:
    image: ghcr.io/tuist/cloud-on-premise:latest
    container_name: tuist_cloud
    depends_on:
      - db
    ports:
      - "80:80"
      - "8080:8080"
      - "443:443"
    expose:
      - "80"
      - "8080"
      - "443:443"
    environment:
      # Base Tuist Env - https://docs.tuist.io/cloud/on-premise#base-environment-configuration
      TUIST_USE_SSL_FOR_DATABASE: "0"
      TUIST_LICENSE:  # ...
      TUIST_CLOUD_HOSTED: "0"
      DATABASE_URL: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
      TUIST_APP_URL: https://localhost:8080
      TUIST_SECRET_KEY_BASE: # ...
      WEB_CONCURRENCY: 80
      
      # Auth - one method
      # GitHub Auth - https://docs.tuist.io/cloud/on-premise#github
      TUIST_GITHUB_OAUTH_ID: 
      TUIST_GITHUB_OAUTH_SECRET: 

      # Okta Auth - https://docs.tuist.io/cloud/on-premise#okta
      TUIST_OKTA_SITE:
      TUIST_OKTA_CLIENT_ID:
      TUIST_OKTA_CLIENT_SECRET:
      TUIST_OKTA_AUTHORIZE_URL: # Optional
      TUIST_OKTA_TOKEN_URL: # Optional
      TUIST_OKTA_USER_INFO_URL: # Optional
      TUIST_OKTA_EVENT_HOOK_SECRET: # Optional

      # Storage
      TUIST_S3_ACCESS_KEY_ID: # ...
      TUIST_S3_SECRET_ACCESS_KEY: # ...
      TUIST_S3_BUCKET_NAME: # ...
      TUIST_S3_REGION: # ...
      TUIST_S3_ENDPOINT: # https://amazonaws.com
    
      # Other

volumes:
  db:
    driver: local

On premise ​

Release cadence ​

Runtime requirements ​

Running Docker-virtualized images ​

Postgres database ​

Storage ​

Configuration ​

License configuration ​

Base environment configuration ​

Authentication environment configuration ​

GitHub ​

Google ​

Okta ​

Storage environment configuration ​

S3-Compliant storages ​

Deployment ​

Pulling the Docker image ​

Deploying the Docker image ​

Fly ​

Docker Compose ​