Skip to content

deployment.md

Latest commit

 

History

History
47 lines (34 loc) · 1.76 KB

deployment.md

File metadata and controls

47 lines (34 loc) · 1.76 KB
Raw

Deployment

Preferred path

Run temperpaw deploy. The CLI is responsible for:

  1. Checking prerequisite CLIs.
  2. Provisioning Turso and R2.
  3. Creating the Railway project.
  4. Seeding the admin account and dashboard-managed secrets.

Railway fallback

If you prefer the one-click path, use the Railway button in the README and provide the infrastructure variables manually:

  • TURSO_URL
  • TURSO_AUTH_TOKEN
  • BLOB_ENDPOINT
  • BLOB_BUCKET
  • BLOB_ACCESS_KEY
  • BLOB_SECRET_KEY

Genesis app source

Production TemperPaw app capabilities should come from Genesis, not from the repo-local app catalog. Configure fresh-instance bootstrap with pinned refs:

  • TEMPERPAW_GENESIS_REGISTRY_URL=https://genesis-production-164d.up.railway.app
  • TEMPERPAW_GENESIS_REGISTRY_TENANT=default
  • TEMPERPAW_GENESIS_BOOTSTRAP_REFS=temperpaw/paw-fs@HASH,temperpaw/paw-agent@HASH
  • TEMPERPAW_GENESIS_CACHE_RESTORE_TIMEOUT_SECS=20
  • TEMPERPAW_GENESIS_BOOTSTRAP_TIMEOUT_SECS=60

On restart with the same database, TemperPaw restores installed Genesis app metadata and skips unchanged bootstrap refs. Do not reset, wipe, replace, or restore over a production database. Only a genuinely new empty database is a fresh instance that installs the configured pinned refs once.

The restore and bootstrap deadlines are startup safety valves. If Genesis cache recovery or configured app bootstrap stalls, TemperPaw logs a warning and continues to readiness using the installed state already present in the database; operators can repair the pinned Genesis app version and redeploy without any database reset.

Optional Datadog

Deploy the collector config in scripts/otel-collector-railway.yaml as a second Railway service and point OTEL_EXPORTER_OTLP_ENDPOINT at the collector's internal hostname.