Skip to main content
The repository’s .do/deploy.template.yaml deploys the Filament standalone image as one DigitalOcean App Platform service: Deploy to DigitalOcean

​
What gets deployed

The template runs ghcr.io/galaxy-io/filament/standalone:0.1.0 on one 512 MiB App Platform service. The image contains the API, web application, scheduler, execution engine, SQLite datastore, and embedded NATS JetStream server. This topology is intended for testing and evaluation. DigitalOcean’s Deploy to DO template format supports one service, optionally with a development database, so it cannot deploy Filament’s separate server, control plane, and NATS services from one button.
DigitalOcean App Platform does not provide persistent volumes. The standalone image stores its SQLite database and JetStream data on the service’s local filesystem, so deployments and container replacements can erase all Filament state. Do not use this template for production or irreplaceable data.

​
Deploy the template

1

Open the template

Click Deploy to DigitalOcean above and sign in to DigitalOcean.
2

Review the service

Confirm the service uses the filament/standalone:0.1.0 image and review the selected instance size and estimated monthly cost.
3

Create the app

Click Create Resources and wait for the service to become healthy.
4

Open Filament

Open the generated ondigitalocean.app URL shown for the service.

​
Connector credentials

The standalone image uses a read-only environment secret provider. Convert a secret reference to uppercase and replace punctuation with underscores, then add that environment variable to the App Platform service. For example, the reference postgres-creds/dsn resolves from POSTGRES_CREDS_DSN. Restart the deployment after adding or changing credential environment variables. See Configuration for all standalone settings.

​
Upgrades

The template pins the standalone image to a Filament release. To upgrade new deployments, change the image tag in .do/deploy.template.yaml. Existing apps can select the new tag from the service’s Source settings and redeploy.