Skip to main content
Tandemn server configuration starts from the .env file created by setup.sh. Use the repository’s example environment values as the source of truth for the version you are running.

​
Configure from the example

bash setup.sh
Open the generated .env, review every value, and update it for your deployment. The exact fields can change between releases, so use the repository’s example environment values as the source of truth for that release.

​
Configuration principles

  • Keep deployment-specific values in .env.
  • Do not commit .env to source control.
  • Use separate .env files for separate environments.
  • Record which server URL users should set in TD_SERVER_URL.
  • Set S3_UPLOAD_BUCKET to an existing bucket in your AWS account.
  • Set HF_TOKEN when running gated HuggingFace models.
  • Set TD_API_KEY when the control plane is exposed outside a private network.
  • Leave KOI_SERVICE_URL unset unless you intentionally enable optional Koi integration.
  • Keep model availability and cluster assumptions documented for users.

​
User-facing value

Users need one configuration value to start: 
export TD_SERVER_URL=<your-server-url>
If API key authentication is enabled, users also need: 
export TD_API_KEY=<your-api-key>
After that, they can verify access with: 
tandemn check

​
Configuration handoff

When onboarding a new user, give them:
  • The server URL
  • Supported model identifiers
  • Expected input file format
  • Expected SLO conventions
  • Whether TD_API_KEY is required
  • A support contact for failed jobs or connectivity issues