Skip to main content
Once you’ve built out your Compose App and tested it locally, you’ll want to deploy it for production usage. Your app will be deployed to a fully isolated runtime environment with a dedicated database. Environment Variables and Secrets you’ve provided will be available to your app and our durability engine will ensure task execution and resumption across restarts and roll-outs. You’ll be able to monitor your app via the goldsky web application.

​
The deploy command

Deployment is done by running this command with a reference to your manifest file. The deploy command is idempotent and will handle upserting your app to the cloud. 
goldsky compose deploy
The Compose CLI extension will handle provisioning the necessary resources and launching your app based on the configuration in your manifest. Once complete, cron tasks will start and HTTP triggers will be available. See task-triggers for more information.

​
Monitoring your app via the webapp

Like with our indexing products, you’ll see your Compose Apps in the Goldsky Webapp. From there you’ll be able to see the App’s status, recent task runs (with details about all context function calls) and raw logs output. The url for your App’s dashboard will be formed like: 
https://app.goldsky.com/dashboard/compose/{appName}

​
Deleting a Compose app

You can delete a Compose app from the webapp by navigating to your app’s dashboard and clicking the Delete button. A confirmation modal will appear requiring you to type the app name to confirm deletion.

​
Database management options

When deleting a Compose app that uses a hosted Postgres database, you can choose whether to keep or delete the associated database:
  • Delete associated database (default): The hosted Postgres database will be permanently deleted along with the app and all its data.
  • Keep database: Uncheck the “Delete associated database” option to preserve the database. This is useful if you want to retain your data for analysis or migrate it to another app.
Database deletion is permanent and cannot be undone. Make sure to back up any important data before deleting.

​
Pipeline validation

If you choose to delete the associated database, the system will check whether the database is being used by any active pipelines. If the database is referenced by one or more pipelines, the deletion will be blocked and you’ll see an error message listing the affected pipelines. To proceed with database deletion in this case, you must first:
  1. Delete or modify the pipelines that reference the database
  2. Then retry deleting the Compose app with the database option selected
Alternatively, you can keep the database by unchecking the “Delete associated database” option, which allows you to delete the app while preserving the database for use by the existing pipelines.