Runway
Menu
Menu 
Runway is built and operated in the EU!
Docs

Configuration

The following table lists all available configuration options for Tailscale on Runway.

Set these options with:

Runway Apps: my-app
runway app config -a my-app set \
    TS_AUTHKEY=tskey-auth... \
    TS_HOSTNAME=my-app
runway app restart -a my-app
Runway Services: db-psql
runway service config set db-psql \
    TS_AUTHKEY=tskey-auth... \
    TS_HOSTNAME=db-psql
runway service db-psql restart

Options

The following table lists all environment variables that you can use to customize the integration with Tailscale. They work for applications and services on Runway.

Name Default Required Description
RUNWAY_TS_MANAGED true no When set to false (also accepts off, no, 0), Runway will not add its own Tailscale sidecar and will pass all TS_* variables directly to your container. Use this when running an app that manages its own Tailscale connection — see the tsidp guide for a worked example.
TS_AUTHKEY empty yes The key to authenticate with. Enables Tailscale integration.
TS_HOSTNAME empty no Sets the DNS name of the application in Tailscale.
TS_AUTH_ONCE false no If true, only try to log-in if not already logged-in.
TS_ENABLE_METRICS false no Enable the Prometheus metrics.
TS_TAG1 empty no See our guide on working with tags.
TS_LOGIN_SERVER1 empty no Connect to your own controlserver (e.g. headscale or ionscale).

1: The TS_TAG and TS_LOGIN_SERVER options are custom to Runway's integration with Tailscale. They are only processed when RUNWAY_TS_MANAGED is enabled (the default). Setting them alongside RUNWAY_TS_MANAGED=false will have no effect.