---
title: Deploy Ghost with AI on Blossom
url: "/deploy/ghost/"
canonical_url: https://docs.blossom88.com/deploy/ghost/
markdown_url: https://docs.blossom88.com/deploy/ghost.md
summary: Deploy Ghost with AI on Blossom. Publish your own blog with managed MySQL,
  uploads in S3 or R2, and a theme that survives app updates.
categories:
- deployment
- publishing
---

# Deploy Ghost with AI on Blossom

[Ghost](https://ghost.org/) is a publishing platform for blogs, newsletters,
and memberships. Write posts, build a publication, and keep a direct
relationship with your readers.

Run Ghost on regular App Capacity, with managed MySQL and uploads in your
own S3 or Cloudflare R2 bucket.

[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent

> **Ask your AI agent:** Deploy Ghost on Blossom with managed MySQL and R2. Help me publish my first post.

> Follow this guide: https://docs.blossom88.com/deploy/ghost/



Your agent checks [Ghost's production requirements](https://docs.ghost.org/hosting),
selects compatible maintained images, and saves the choices with your App.

| Part | Purpose |
|---|---|
| Ghost | Serves the publication and its administration dashboard |
| Managed MySQL | Keeps posts, members, accounts, and site settings |
| Your S3 or R2 bucket | Keeps uploads and a saved theme bundle |
| Asset delivery | Serves uploads and responsive image sizes from the private bucket |
| Your email provider | Delivers account messages and, when configured, newsletters |

Use a MySQL release Ghost officially supports from
[Blossom Managed Data](/docs/data/). Select the compatible version
explicitly; the default MySQL version may be newer than Ghost supports.
Link the Database instance to the Environment before starting Ghost and its
initial migrations.

### Connect Your Bucket

Create a private bucket in your own AWS or Cloudflare account and a
bucket-restricted credential. Supply the bucket, endpoint, region, and
credentials through a private environment file. Your agent configures Ghost's
[built-in S3 storage adapter](https://docs.ghost.org/config#ghosts-built-in-s3-compatible-storage-adapter)
for **images, media, and files**.

Keep the bucket private. Serve publication uploads through a public asset
Service or CDN, including responsive image sizes. Theme bundles belong
outside those public paths. Our tested setup uses an asset Service on regular
App Capacity alongside Ghost.

### Keep Your Theme

Ghost still reads theme files locally. Save the selected theme as a deployment
bundle and restore it from the bucket **before Ghost starts**. The local copy
can then be recreated whenever Blossom replaces the Container.

After uploading a new theme ZIP in Ghost Admin, save that version back to
the deployment bundle before an update. A theme upload alone changes only the
current Container's files; the selected theme is recorded in MySQL.

Other local configuration, such as custom routes and redirects, also needs
to be saved and restored before startup.

For a workflow where editors manage these files entirely in Ghost Admin, use a
[Persistent Service](/docs/apps/persistent-services/) for Ghost's
content directory instead. It keeps those local changes automatically.

Set Ghost's canonical `url` to your final HTTPS address. For a generated
App URL, derive it at startup from `BLOSSOM_SERVICE_HOST`. Create your own
owner account at `/ghost/` before opening the publication to readers.

## Publish Your First Post

> **Ask your AI agent:** Help me publish a post with a cover image, then check it as a reader.

> Follow this guide: https://docs.blossom88.com/deploy/ghost/



Open Ghost Admin, write a post, upload an image, and publish it to the web.
Open its public URL in a separate browser session to check the post, image,
and navigation without an administrator login.

![A Ghost publication served by Blossom with a published post.](/assets/images/ghost/publication.webp)

![Ghost Admin showing the publication's posts.](/assets/images/ghost/admin.webp)

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Create an App and a prebuilt-image Environment using the compatible Ghost
image selected by your agent:

    blossom app:create --data app.yml
    blossom environment:create --data environment.yml

Create the compatible managed MySQL Database instance and link it to the
Environment:

    blossom database_instance:create --data database_instance.yml --follow
    blossom environment_link:create --data environment_link.yml

Environment links provide private connectivity and inject the database URL.
The link file uses the IDs Blossom returns:

```yaml
environment_link:
  environment_id: environment-100
  target_type: DatabaseInstance
  target_id: database_instance-100
  var_name: DATABASE_URL
```

Your agent maps the linked URL at every start to Ghost's native
`database__client` and `database__connection__*` settings. Keep the database
connection private.

Ghost and the asset Service use regular App Capacity. Their Service files
include the selected images, startup commands, resources, and readiness
checks:

```yaml
service:
  # Environment, image, startup command, port, and resources go here.
  name: web
  publicly_exposed: true
  desired_size: 1
```

The startup command restores the saved theme before launching Ghost. Enable
`S3Storage` for all three upload types. The asset Service reads publication uploads from the bucket and handles image
sizes, including the WebP/AVIF paths generated by the theme. Configure Ghost
with that Service's HTTPS address and matching
`urls.image`, `urls.media`, and `urls.files` values before publishing.
Use the common asset base, including any tenant prefix, **before** the
`/content/images`, `/content/media`, or `/content/files` part:

```json
{
  "urls": {
    "image": "https://uploads.example.com/my-site",
    "media": "https://uploads.example.com/my-site",
    "files": "https://uploads.example.com/my-site"
  }
}
```

Create the Services and push the private settings:

    blossom service:create --data service.yml
    blossom service:create --data assets-service.yml
    blossom env_var:push --environment environment-100 --file .env.production
    blossom environment:deploy --id environment-100 --follow

Use readiness commands available in the selected image, such as Node HTTP
probes for Ghost's image.

</details>

## Configure Email Before Inviting Members

> **Ask your AI agent:** Help me configure email for my Ghost publication and test a reader signup.

> Follow this guide: https://docs.blossom88.com/deploy/ghost/



Configure [transactional email](https://docs.ghost.org/config#mail) for member
sign-in links, staff verification, and password resets. Native newsletter
sending uses a separate [Mailgun bulk-mail integration](https://docs.ghost.org/faq/mailgun-newsletters);
SMTP settings alone do not enable newsletters. Connect your own provider and
sending domain, then test with an address you control.

## Keep Your Publication Through Updates

> **Ask your AI agent:** Update Ghost and check that my posts, uploads, and saved theme are still there.

> Follow this guide: https://docs.blossom88.com/deploy/ghost/



Save theme changes to the startup bundle first. Keep **one active Ghost
Container**: stop Ghost before deploying an update, then start it again when
the deployment completes. Expect a brief interruption while it restarts.

Keep independent backups of both MySQL and the bucket, including the theme
bundle. Configure the database's
[backup storage](/docs/backups/); database backups do not include
uploaded files. Follow Ghost's supported upgrade path when changing versions.

<details class="optional-reading" markdown="1">
<summary>Commands to update without overlapping Ghost Containers</summary>

Stop Ghost and wait before deploying. The asset Service can keep serving
existing uploads:

    blossom service:scale --id service-100 --desired-size 0 --follow
    blossom environment:deploy --id environment-100 --follow
    blossom service:scale --id service-100 --desired-size 1 --follow
    blossom logs --environment environment-100 --lines 30

</details>

Ghost [does not support clustering](https://docs.ghost.org/hosting#optimizing-for-scale).
For higher reader traffic, plan a CDN and caching in front of the publication.

## What You Get

- Your own Ghost publication at an HTTPS address
- Ghost Admin for writing posts and managing readers
- Managed MySQL and uploads in your own S3 or R2 bucket
- A saved theme restored on fresh Containers, without a Persistent Service
