Role
Primary
Dagster in the Dagster stack
This page explains what Dagster means in the Dagster stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Dagster is one of the main services that defines the default shape of instances created from the Dagster stack.
Base service
Dagster
Type
service
Stack fit
How Dagster fits into this stack
Dagster is one of the main services that defines the default shape of instances created from the Dagster stack.
This stack service is based on Dagster and keeps the service-specific setup for Dagster in one place.
It is linked to PostgreSQL inside the stack.
Version policy
Available versions include 1.
Inclusion
Enabled by default: Yes
Required: No
Primary: Yes
Connections
postgres: PostgreSQL
Storage
This stack service does not define persistent volume sizes.
Stack-specific technical details
Review the operational capabilities exposed by Dagster inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Configs
Keep service config files versioned with the stack instead of rebuilding them per environment.
Workspace
Actions
Keep one-off and lifecycle commands with the service instead of relying on manual runbooks.
Wipe pending runs
Trigger: button.
Service links
See how services are wired together so dependencies stay consistent across environments.
PostgreSQL
Linked to PostgreSQL. Required.