Role
Required
MySQL in the Ghost stack
This page explains what MySQL means in the Ghost stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
MySQL is included by default and treated as a required part of the Ghost stack.
Base service
MySQL
Type
db
Delivery
Prebuilt service image
Stack fit
How MySQL fits into this stack
MySQL is included by default and treated as a required part of the Ghost stack.
This stack service is based on MySQL and keeps the service-specific setup for Ghost in one place.
Version policy
This stack service is limited to 8.4.
Inclusion
Enabled by default: Yes
Required: Yes
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
data: 20 GB
Stack-specific technical details
Review the operational capabilities exposed by MySQL inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Backups
Protect service data with repeatable backup workflows that stay attached to the stack.
Default database backup
Imports and migration
Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.
Database import
Import from a backup archive, uploaded file, or public URL depending on the service workflow.
Configs
Keep service config files versioned with the stack instead of rebuilding them per environment.
MySQL config
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Data
Size: 10 GB.