Section Overview
Stacks
Use stacks for Compose workloads, service-style systems, and stateful multi-container apps.
What stacks are
Stacks are the service-oriented workload model in StackShift, built around Compose, named volumes, and node-aware placement.
Goal
Know when to use a stack instead of a project or template.
Expected result
You can pick stacks intentionally instead of treating them as “projects but bigger”.
Deploy a Compose stack
Bring a Compose-defined workload to StackShift with domains, placement, and persistent volumes.
Goal
Get a multi-container workload running as a StackShift stack.
Expected result
The Compose workload is running as a managed stack in StackShift.
Stack logs, health, and placement
Use the stack detail, logs, and placement information to understand how the stack is actually running.
Goal
Inspect stack runtime state without dropping straight to the node.
Expected result
You can tie a stack runtime symptom back to logs, service health, and placement.
Back up and restore a stack
Use S3-backed named-volume archives to protect and recover stateful stack data.
Goal
Create and restore stack backups with correct expectations about what is and is not preserved.
Expected result
Your stack data can be archived and restored through the platform.
Reassign and migration expectations
Understand what stack reassignment and migration mean today, especially for stateful stacks.
Goal
Set the right operator expectations before moving stack workloads across nodes.
Expected result
You understand how safe stack movement works today and where caution is still required.
Stack troubleshooting
Common stack-side failures around placement, logs, health, template drift, and restore behavior.
Goal
Troubleshoot stacks as service systems, not just as single containers.
Expected result
You can tell whether the problem is runtime, placement, recovery, or template-related.