Service type
Ghost service
Self-hosted Ghost publishing service for blogs and content sites, with persistent content storage and links to MySQL and transactional email.
Use it in stacks that need repeatable data workflows, scheduled backups, and realistic environment refreshes without rebuilding those steps manually.
Why teams use this service
Technical profile
Review versions, ports, source, and packaging.
Stacks that use it
See where this service fits in ready-made stacks.
Backups and data import
Move working data between environments with storage-backed workflows.
Runtime wiring and defaults
See ports, links, storage, configs, and runtime behavior.
On Wodby
How Ghost runs on Wodby
ghost image; all of the configuration below is passed as environment variables, which Ghost reads as configuration keys with __ between nested levels.Linked services
| Link | Variables |
|---|---|
| MySQL database (required) | database__client, database__connection__host, database__connection__port, database__connection__user, database__connection__password, database__connection__database |
| Mail transfer agent (required) | mail__transport, mail__options__host, mail__options__port, mail__options__secure |
Mail goes to the linked mail service over SMTP without TLS or credentials. Do not add database or SMTP settings elsewhere.
URL and server
urlis the environment's primary URL. Ghost uses it for links, so it changes with the primary host.- Ghost listens on
server__hostandserver__port, port 2368, which is the service's endpoint.NODE_ENVisproduction. - The setting "Email sender" (required) sets
mail__from. - The setting "Verify new devices by email" sets
security__staffDeviceVerification. It defaults tofalse, because with it on, staff signing in from a new device need a code sent by email, and without working mail delivery they cannot sign in. Set it totrueonce mail is delivered.
Changing configuration
Add or change environment variables on the service, using the same section__key form, and deploy the service. Do not edit config.production.json in the container: it is not on a volume.
Data
- The
contentvolume is mounted at/var/lib/ghost/content: images, themes and other content files. Posts, users and settings are in the linked MySQL database. - The manifest declares a content import into that directory (
tar,tar.gz,tgz,zip) and a content backup of it. Neither includes the database. - The manifest creates no administrator account: the owner account is created in the browser at
/ghoston first use.
Overview
Technical profile and packaging
Versions
Source repository
Public Helm chart
Ports and protocols
Labels
Persistent volumes
Stacks
Use it inside ready-made stacks or your own
Data workflows
Keep recovery points ready and move data between environments
Attach backups to the service model
Keep scheduled backup behavior with the same versioned service definition instead of rebuilding it environment by environment.
Refresh staging and development with working data
Import archives into another environment when teams need realistic copies for testing, review, or onboarding.
Upload archives to cloud storage
Send backup archives to external storage providers instead of keeping them only inside the platform.
Runtime wiring
Reuse connectivity, storage, and runtime defaults
Endpoints
Technical domains
Volumes
Settings
Service links
These links define which other services can connect to Ghost when it is used inside a stack.
db
Eligible linked services
sendmail
Eligible linked services