StackScripts versus Quick Deploy
I recall StackScripts as having already been a platform feature years ago.
Recently, I noticed another feature, called Quick Deploy, which seems to serve the same general purpose.
I am seeking clarification over the differences between the two, and especially over whether either is lacking compared to the other in its benefits.
2 Replies
hsato
Linode Staff
Hello! Quick Deploy Apps and StackScripts overlap, but they solve different problems.
- Quick Deploy Apps: Choose this for fast, zero-scripting deployments of common apps (like Node.js or multi-node clusters). It launches a Linode with the app pre-installed and ready to use. Read the overview or get started.
- StackScripts: Choose this when you need custom, repeatable provisioning logic that the app catalog doesn't cover. You write the logic (bash, Python, etc.) to run on the first boot. Learn more about StackScripts. (Note: Our Metadata service is now the more modern alternative).
Quick Deploy Apps gives you fast, curated deployments with cluster support, while StackScripts gives you custom scripting flexibility. We actively support both, so pick whichever fits your current task!
@hsato: Thank you for the explanation.
Compared to StackScripts, Quick Deploy seems to be more powerful and comprehensive.
I understand that StackScripts allows customers to create rather quickly a uniform process for provisioning nodes of a certain function, but the platform maintains a library of community-contributed StackScripts.
I am left to wonder still why anyone would choose to use a community StackScript over Quick Deploy, when seeking to provision a new node with some particular application.