RUN_MIGRATIONS=1 initializes schema; the first-run administrator values should be removed after creation.
Towbar manifests
Configure
- Prepare the example server, connect the repository, and map
productionto the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration. - Save the initialization values in the table below for the postgres Datastore under Datastore → Settings → Secrets. Deploy it first and wait for readiness. These values create the database and user only on an empty volume.
- Set the Service’s declared runtime values under Service → Settings → Secrets using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
- Deploy the Service, then perform the checks below before enabling auto-deploy.
Datastore values
Save these in each Datastore’s Settings → Secrets before deploying it. Use the suggested names or choose your own, then use the same names and passwords in the Service connection values below.Runtime values
Save these values on the Service after the repository sync. The manifest declares required keys, not their values.Verify
Add a feed, refresh it, and confirm subscription and read state survive redeployment. After the administrator exists, removeCREATE_ADMIN, ADMIN_USERNAME, and ADMIN_PASSWORD from the manifest and Service secrets, sync, and redeploy; they are first-run values only.
For field constraints, see Service manifest and Datastore manifest.
