Section Overview
Templates
Templates are curated stack blueprints with versioning, service notes, and safer lifecycle controls.
What templates are
Templates are versioned service blueprints that render into stacks with saved inputs and provenance.
Goal
Understand templates as a managed service-deployment layer on top of stacks.
Expected result
You can explain why templates are different from pasting raw Compose into a stack.
Deploy from a template
Launch a curated service by supplying template inputs, choosing placement, and reviewing the rendered summary.
Goal
Deploy a template-backed stack with the right operational expectations.
Expected result
A template-backed stack is created and ready for lifecycle management.
Deploy WordPress on StackShift
Launch single-site WordPress as a template-backed stack with bundled MariaDB and persistent storage.
Goal
Deploy WordPress with the right first-boot and persistence expectations.
Expected result
A template-backed WordPress stack is running with persistent WordPress and database volumes.
Deploy WordPress for agencies
Use the WordPress + Elementor template when you want visual editing and builder-friendly PHP defaults available immediately after launch.
Goal
Launch an agency-friendly WordPress stack with Elementor installed by the platform template flow and PHP builder defaults already applied.
Expected result
A template-backed WordPress stack is running with Elementor ready for visual editing and builder-friendly PHP defaults already in place.
Connect a custom domain to WordPress
Understand how StackShift routing and WordPress site URLs interact before and after first boot.
Goal
Attach the right domain without leaving WordPress and StackShift out of sync.
Expected result
Routing and WordPress site URLs line up with fewer surprises after launch.
Back up and restore a WordPress stack
Use StackShift stack backups for WordPress content and bundled MariaDB data, then validate the app after restore.
Goal
Recover WordPress deliberately instead of assuming a restore badge means the application is perfect.
Expected result
WordPress recovery uses StackShift backups with realistic operator expectations.
Template inputs and secrets
Understand which template values are required, which are sensitive, and how they affect rendering and upgrades.
Goal
Avoid misconfiguring a service by treating template inputs as throwaway form fields.
Expected result
Template deployment inputs are supplied deliberately and with less surprise at upgrade time.
Updating template-backed stacks
Preview diffs, resolve missing inputs, and apply the latest published template version safely.
Goal
Use the template lifecycle path instead of treating updates as blind redeploys.
Expected result
The stack moves to a new template version with upgrade history preserved.
Template upgrade safety and service notes
Understand why an upgrade is safe, risky, or blocked, and how template readiness notes should influence operator decisions.
Goal
Interpret template readiness and upgrade risk before clicking apply.
Expected result
Template lifecycle decisions feel deliberate instead of surprising.