- Before you submit
- Before you run the commands
- A practical command path
- What reviewers and future users need
- Why Status Panel matters here
- Good next reads
A marketplace submission should not be the first time a stack feels organized.
The stronger pattern is to stabilize the stack first, make it repeatable, confirm it can be operated, and only then prepare it for submission.
A good submission is usually the result of discipline that already exists before the submit command.
Before you submit
- the stack should deploy cleanly
- health checks should be stable
- logs should be understandable enough for support
- one real workflow should work end to end
- environment-specific values should be separated from reusable structure
Before you run the commands
If you do not have Stacker installed yet, the quickest path is the install script.
curl -fsSL https://raw.githubusercontent.com/trydirect/stacker/main/install.sh | bashGitHub repository and installation steps
If you prefer to explore Stacker with Docker first, you can also pull the image:
docker pull trydirect/stacker:latestIf your workflow also uses Status Panel locally or on a target server, start here too.
curl -sSfL https://raw.githubusercontent.com/trydirect/status/master/install.sh | shGitHub repository and installation steps for Status Panel
docker pull trydirect/status:latestA practical command path
stacker init --with-aishellscript
stacker deploy --target localshellscript
stacker deploy --target servershellscript
stacker agent statusshellscript
stacker submitshellscript
stacker marketplace statusshellscript
What reviewers and future users need
- a clear use case
- a tested service layout
- clean defaults
- an understandable operational story after deployment
- enough confidence that another team can run the stack too
Why Status Panel matters here
A stack becomes more credible for submission when it can be checked, understood, and supported after deployment. That is why runtime checks and Status Panel workflows matter before submission too.
Good next reads
If the stack is not repeatable yet, go back to the repeatable template guide first. For the broader product story, read the marketplace article too.