Three small gaps in how the process behaves at its edges: - An unhandled rejection or uncaught exception crashed the process with the stack on stderr only. index.ts now logs it to trek.log and runs the same orderly shutdown a SIGTERM gets, exiting with 1; a second fatal error during that shutdown exits at once. - /api/health/ready kept answering 200 while a SIGTERM was draining the process, so an orchestrator sent traffic for another probe period. A shutdown now marks the new ReadinessService first (and Nest's own shutdown hook marks it too), and the probe answers 503 from then on. - Node closes an idle keep-alive connection after 5 seconds while reverse proxies keep upstream connections for about a minute, which shows up as intermittent 502s. The server now keeps them for 65 seconds, configurable through HTTP_KEEP_ALIVE_TIMEOUT_MS (owned by the httpConfig token), with the headers timeout one second above.
13 KiB
Install: Helm
Deploy TREK on Kubernetes using the official Helm chart.
Add the Chart Repository
helm repo add trek https://chart.liketrek.com
helm repo update
Note:
chart.liketrek.comis a custom domain (CNAME) for the GitHub Pages site athttps://liketrek.github.io/TREK— both serve the same chart repository. Using the custom domain keeps your setup working even if the GitHub repository moves again.
⚠️ Repository moved: The chart is no longer served at
https://mauriceboe.github.io/TREK(the project moved from a personal repo to theliketrekorganization). If you added the repo from the old URL, switch to the new one:helm repo remove trek helm repo add trek https://chart.liketrek.com helm repo updateExisting releases keep working — only the repo URL changes; future
helm repo update/helm upgraderuns require the new URL. (https://liketrek.github.io/TREKalso works — it redirects tochart.liketrek.com.)
Basic Install
helm install trek trek/trek
This deploys TREK with default values: a ClusterIP service on port 3000, 1 Gi PVCs for data and uploads, and no ingress.
Encryption Key
ENCRYPTION_KEY encrypts stored secrets (API keys, MFA, SMTP, OIDC) at rest. There are three ways to handle it:
Option 1 — Let the chart generate a random key (recommended for new installs):
helm install trek trek/trek --set generateEncryptionKey=true
The chart generates a 32-character alphanumeric key at install time and preserves it across upgrades. Note that this differs from the 64-character hex key produced by openssl rand -hex 32 — both formats are accepted by the server.
Option 2 — Set an explicit key:
helm install trek trek/trek \
--set secretEnv.ENCRYPTION_KEY=$(openssl rand -hex 32)
Option 3 — Use an existing Kubernetes Secret:
kubectl create secret generic trek-secrets \
--from-literal=ENCRYPTION_KEY=$(openssl rand -hex 32)
helm install trek trek/trek \
--set existingSecret=trek-secrets
If existingSecret uses a different key name than ENCRYPTION_KEY, specify it with --set existingSecretKey=MY_KEY_NAME.
Note: If both
generateEncryptionKeyandexistingSecretare set,existingSecrettakes precedence. Only one method should be active at a time.
GitOps:
generateEncryptionKeyreads the existing secret from the cluster to keep the key across upgrades. Underhelm template, ArgoCD or Flux the chart cannot do that and renders a new key on every sync. TREK then refuses to start rather than lose every stored secret (see Encryption-Key-Rotation). UseexistingSecretin those setups.
Note: If
ENCRYPTION_KEYis left empty, the server resolves it automatically: existing installs fall back todata/.jwt_secret(encrypted data stays readable after upgrade); fresh installs auto-generate a key persisted to the data PVC.
Note:
JWT_SECRETis managed entirely by the server — auto-generated on first start and persisted to the data PVC. It can be rotated via the admin panel (Settings → Danger Zone → Rotate JWT Secret). No Helm configuration is needed or supported for it.
Admin Account
ADMIN_EMAIL and ADMIN_PASSWORD are set via secretEnv. They are only used on first boot when no users exist yet. Both must be set together — if either is missing, the server ignores both values and instead creates the admin account with email admin@trek.local and a random password, which is printed to the server log.
helm install trek trek/trek \
--set secretEnv.ADMIN_EMAIL=admin@example.com \
--set secretEnv.ADMIN_PASSWORD=<your-secure-password>
Note: When
OIDC_ONLY=trueis configured together withOIDC_ISSUERandOIDC_CLIENT_ID, no local admin account is created on first boot. Instead, the first user to log in via SSO automatically becomes admin.
Key values.yaml Settings
Image
image:
repository: mauriceboe/trek
# tag: latest # defaults to the chart's appVersion
pullPolicy: IfNotPresent
# Optional: pull secrets for private registries
imagePullSecrets: []
# - name: my-registry-secret
Service
service:
type: ClusterIP # change to LoadBalancer or NodePort to expose externally
port: 3000
Plain Environment Variables (env)
env:
NODE_ENV: production
PORT: 3000
# TZ: "Europe/Berlin" # timezone for logs, reminders, cron jobs
# LOG_LEVEL: "info" # "info" = concise, "debug" = verbose
# TREK_WIKI_DIR: "/app/wiki" # where /help reads its docs from; leave unset (the image ships them)
# ALLOWED_ORIGINS: "https://trek.example.com"
# APP_URL: "https://trek.example.com"
# FORCE_HTTPS: "false" # enable HTTPS redirect + HSTS; set TRUST_PROXY for correct client IPs
# HSTS_INCLUDE_SUBDOMAINS: "false" # add includeSubDomains to the HSTS header
# SESSION_DURATION: "24h" # session length without "Remember me"
# SESSION_DURATION_REMEMBER: "30d" # session length with "Remember me", and every SSO session with OIDC_ONLY
# TRUST_PROXY: "1" # proxy hops for X-Forwarded-For/Proto; defaults to 1 in production
# COOKIE_SECURE: "true" # auto-derived; set "false" only for local HTTP testing
# ALLOW_INTERNAL_NETWORK: "false" # set "true" if Immich or other services are on a private network
# ALLOW_LINK_LOCAL_IPS: "" # single link-local addresses TREK may reach, e.g. "169.254.1.2"
# HTTP_PROXY: "" # outbound proxy for HTTP requests
# HTTPS_PROXY: "" # outbound proxy for HTTPS requests
# NO_PROXY: "localhost,127.0.0.1" # hosts that bypass the proxy
# DEMO_MODE: "false" # enable demo mode (hourly data resets)
# MCP_RATE_LIMIT: "300" # max MCP requests per user per minute
# NOMINATIM_URL: "" # your own Nominatim for every geocoding call
# OVERPASS_URL: "" # your own Overpass endpoint(s), comma-separated
# OVERPASS_TIMEOUT_MS: "25000" # per-endpoint Overpass timeout
# TREK_PLACES_ENABLED: "false" # stop asking the TREK Places API
# TREK_PLACES_URL: "" # a copy of the TREK Places API you run yourself
# AMAP_API_BASE: "" # send the Amap calls through a proxy or gateway
# OIDC_ISSUER: "https://auth.example.com"
# OIDC_CLIENT_ID: "trek"
# OIDC_DISPLAY_NAME: "SSO"
# OIDC_ONLY: "false" # force SSO-only mode; disables password login
# OIDC_ADMIN_CLAIM: "" # OIDC claim used to identify admin users
# OIDC_ADMIN_VALUE: "" # value of that claim that grants admin role
# OIDC_USERNAME_CLAIM: "" # claim a new account's username comes from, e.g. preferred_username
# OIDC_SCOPE: "openid email profile groups"
# OIDC_DISCOVERY_URL: "" # override for providers with non-standard discovery paths (e.g. Authentik)
# VAPID_PUBLIC_KEY: "" # Web Push: public half of your own key pair; leave unset to use the generated one
# VAPID_SUBJECT: "mailto:admin@example.com" # Web Push contact; defaults to APP_URL when it is https
Note: The chart only passes on the keys its ConfigMap declares.
DEFAULT_LANGUAGE,MCP_MAX_SESSION_PER_USER(althoughvalues.yamllists it in a comment),FILE_UPLOAD_LIMIT_MBandRESTORE_FROM_BACKUPare not among them, so a value underenv:is dropped and the default stays. Patch such a variable onto the Deployment if you need it. See Environment-Variables for the language codes.
Sensitive Variables (secretEnv)
These are stored in a Kubernetes Secret and injected as environment variables:
secretEnv:
ENCRYPTION_KEY: "" # recommended: openssl rand -hex 32
ADMIN_EMAIL: "" # initial admin email (first boot only)
ADMIN_PASSWORD: "" # initial admin password (first boot only)
OIDC_CLIENT_SECRET: "" # set if using OIDC
UNSPLASH_ACCESS_KEY: "" # optional; free key from unsplash.com/developers
PLACES_API_KEY: "" # optional; Google Maps API key, wins over the one in Admin > Settings
AMAP_API_KEY: "" # optional; Amap Web 服务 key for place search in mainland China
AMAP_API_SECRET: "" # optional; the signing secret of that key, only when signing is on
VAPID_PRIVATE_KEY: "" # optional; Web Push private half, only together with env.VAPID_PUBLIC_KEY
Alternatively, use generateEncryptionKey: true to let the chart generate and manage the encryption key, or point existingSecret / existingSecretKey at an existing Kubernetes Secret.
Every value the chart writes into its Secret is quoted, so a password such as 12345 or a value like true reaches the container as the text you typed.
Note: Web Push needs none of the
VAPID_*values. TREK generates its key pair on first start and keeps it in the database on the data PVC, so it survives upgrades and restores. Setenv.VAPID_PUBLIC_KEYandsecretEnv.VAPID_PRIVATE_KEYtogether only to bring a pair of your own; changing the pair later means every device has to subscribe again. See Environment-Variables.
Note: Without
UNSPLASH_ACCESS_KEYthe server queries Unsplash's unauthenticated endpoint, which many datacenter and VPS IP ranges — including a lot of Kubernetes clusters — are blocked or rate-limited on. Trip-cover and place-image search then fail with "Unsplash search unavailable". A free Access Key switches the server to Unsplash's authenticated API (api.unsplash.com), which is not subject to that block. The key can also be set in Admin → Settings → API Keys; this value takes priority over that one. See Environment-Variables.
Persistent Storage
persistence:
enabled: true
data:
size: 1Gi # SQLite database, logs, secrets
uploads:
size: 1Gi # uploaded files — increase if you expect large media uploads
Resource Limits
resources:
requests:
cpu: 100m
memory: 256Mi
limits:
cpu: 500m
memory: 512Mi
Health Probes
Startup, liveness and readiness probes are configurable under probes:
- startup hits
/api/healthand gives a first boot, a long migration or a restore at boot up to ten minutes (failureThreshold: 60×periodSeconds: 10) before liveness takes over. - liveness hits
/api/health, which only says the process answers. A long restore does not fail it. - readiness hits
/api/health/ready, which also asks the database. While the database does not answer, the pod stops getting traffic without being restarted. It also answers 503 as soon as the pod starts shutting down, so traffic moves away for the whole drain.
helm install trek trek/trek --set probes.startup.failureThreshold=120 --set probes.readiness.periodSeconds=20
Overrides are merged over the defaults, so setting one key keeps the rest. To switch a probe to exec or tcpSocket, clear the shipped handler in the same override (--set probes.liveness.httpGet=null), otherwise Kubernetes rejects the pod with "may not specify more than 1 handler type". Set probes.startup=null to drop a probe entirely.
env.PORT can be changed: the container port is named http, and the Service and every probe point at that name, so they follow it.
Further environment variables
The env block lists the common settings. Anything else goes in extraEnv (plain values) or extraEnvFrom (whole ConfigMaps or Secrets):
extraEnv:
- name: SESSION_DURATION
value: 7d
extraEnvFrom:
- secretRef:
name: trek-smtp
Ingress
ingress:
enabled: true
className: "nginx" # your ingress class
annotations:
nginx.ingress.kubernetes.io/proxy-read-timeout: "86400" # required for WebSockets
nginx.ingress.kubernetes.io/proxy-body-size: "500m" # required for backup restore
hosts:
- host: trek.example.com
paths:
- /
tls:
- secretName: trek-tls
hosts:
- trek.example.com
Important: TREK uses WebSockets on
/ws. Your ingress controller must support WebSocket upgrades. Setproxy-read-timeoutto at least86400andproxy-body-sizeto at least500mfor backup restores and video uploads.
Note: Keep
env.ALLOWED_ORIGINSin sync withingress.hosts— the chart does not synchronize these automatically.
Note: When using ingress with TLS termination, set
env.FORCE_HTTPS: "true"andenv.TRUST_PROXY: "1"to enable HTTPS redirects, HSTS, and secure cookies.
Upgrade
helm repo update
helm upgrade trek trek/trek
Full Values Reference
See the charts/README.md for all available values.
Next Steps
- Environment-Variables — full variable reference
- Reverse-Proxy — proxy configuration for non-Kubernetes deployments