App Lifecycle

Once your Compose app is deployed, a set of CLI commands let you inspect, pause, resume, delete, tail logs, and review its deploy history, task runs, collections, and deployed source. The per-app commands (status, pause, resume, logs, delete, history, runs, collections, source, download) accept either -n, --name <app> to target by name, or -m, --manifest <path> (default compose.yaml) to read the name from your manifest. list is project-wide and accepts neither. Every command also accepts --json so you can pipe output into scripts or agents.

Check status

goldsky compose status

Shows the app’s name, current runtime status (e.g. RUNNING, PAUSED, STARTING, ERROR), and timestamps for when it was created and last updated.

# status for a specific app, as JSON
goldsky compose status -n my-app --json

List apps

goldsky compose list

Prints a table of every Compose app in your project.

# list as JSON for scripting
goldsky compose list --json

Pause and resume

goldsky compose pause
goldsky compose resume

While paused, cron triggers stop firing and HTTP triggers return an error. State is preserved — resume picks up where the app left off. This is useful for:

Triaging a misbehaving app without deleting it
Holding execution while you roll out a dependency change
Temporarily stopping a cron while you investigate its effects

View logs

goldsky compose logs

By default logs prints the most recent 100 lines. You can tail live, filter by level or text, and bound the output by time or line count.

# tail live
goldsky compose logs -f

# live, errors and warnings only
goldsky compose logs -f --level error,warn

# last hour
goldsky compose logs --since 1h

# search for a substring across the last 500 lines
goldsky compose logs --tail 500 --search "timeout"

# tail live for 5 minutes, then exit
goldsky compose logs -f --timeout 5m

Options cheat-sheet:

Flag	Description
`-f, --follow`	Stream logs live
`--tail <n>`	Number of lines to fetch (default: `100`)
`--level <levels>`	Comma-separated levels (e.g. `error,warn`)
`--search <text>`	Filter lines by text
`--since <duration>`	Logs since a relative time (e.g. `1h`, `30m`, `7d`)
`--max-lines <n>`	Exit after N lines
`--timeout <duration>`	Exit after a duration (e.g. `5m`)
`--json`	Emit newline-delimited JSON

Inspect deploy history and task runs

Use goldsky compose history to see what was deployed and when:

goldsky compose history -n my-app

# include failed deploys in the list
goldsky compose history -n my-app --include-failures

When a task run fails, narrow the runs list with --task, --status, or --since to find it, then fetch the full run detail by id:

# recent runs of a specific task
goldsky compose runs -n my-app --task price_fetcher --limit 10

# failing runs in the last hour
goldsky compose runs -n my-app --status error --since 1h

# full detail for one run
goldsky compose runs -n my-app <runId>

Pipe --json output into jq to drive scripts or alerts:

goldsky compose runs -n my-app --status error --json | jq '.runs[].runId'

For all flags, see the CLI reference.

Query collections

List every collection in your app’s hosted database, then query one with a JSON filter:

goldsky compose collections list -n my-app

goldsky compose collections query prices -n my-app --filter '{"symbol": "BTC"}' --limit 10

For all flags, see the CLI reference.

View and download deployed source

Print the deployed source for your app, or for a single task:

# list the deployed files
goldsky compose source -n my-app

# print one task's source
goldsky compose source -n my-app bitcoin_oracle

Download a runnable copy of the whole app as a zip:

goldsky compose download -n my-app

The same source is available in the dashboard’s Code tab, with a Download app button that produces the same archive. See Deploying and monitoring for details. For all flags, see the CLI reference.

Delete an app

goldsky compose delete

By default delete is interactive: it asks you to type the app name to confirm, and separately asks whether you also want to delete the app’s hosted Postgres database.

# non-interactive (CI-safe) — skip all prompts
goldsky compose delete -f

# non-interactive, also drop the Postgres database
goldsky compose delete -f --delete-database

See Deploying and monitoring for how database deletion interacts with active pipelines.

Deleting an app is permanent. Deleting its database is permanent too, and cannot be undone. Back up anything you care about first.

Compose

Guides

Reference

Check status

List apps

Pause and resume

View logs

Inspect deploy history and task runs

Query collections

View and download deployed source

Delete an app

Next Steps

Deploying your App

Full CLI Reference

​Check status

​List apps

​Pause and resume

​View logs

​Inspect deploy history and task runs

​Query collections

​View and download deployed source

​Delete an app

​Next Steps

Deploying your App

Full CLI Reference

Check status

List apps

Pause and resume

View logs

Inspect deploy history and task runs

Query collections

View and download deployed source

Delete an app

Next Steps