---
title: Deploy Docmost with AI on Blossom
url: "/deploy/docmost/"
canonical_url: https://docs.blossom88.com/deploy/docmost/
markdown_url: https://docs.blossom88.com/deploy/docmost.md
summary: Deploy Docmost with AI on Blossom. Build a private team wiki with a real-time
  editor, managed PostgreSQL and Redis, and R2 attachments.
categories:
- deployment
- productivity
---

# Deploy Docmost with AI on Blossom

[Docmost](https://docmost.com/) is a collaborative team wiki. Use its real-time
editor to keep documentation, runbooks, and shared knowledge in one place.

It's written in TypeScript with NestJS and React. PostgreSQL stores pages and
workspace records; Redis supports background work and collaboration. Browse the
[source on GitHub](https://github.com/docmost/docmost).

This setup runs on regular App Capacity with managed PostgreSQL and Redis.
Attachments live in your private S3-compatible bucket, such as Cloudflare R2.

[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 Docmost on Blossom with managed Postgres and R2 for attachments. Help me set up a private team wiki.

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



Your agent checks the current
[deployment requirements](https://docmost.com/docs/installation), chooses a
maintained release, and saves the configuration. Supply bucket credentials
through a private file.

| Part | Purpose |
|---|---|
| Docmost Service | Wiki dashboard and real-time editor |
| Managed PostgreSQL | Pages, accounts, spaces, and permissions |
| Managed Redis | Background jobs and collaboration support |
| Your private S3-compatible bucket | Page attachments |

Keep the wiki behind **Blossom Account access** and native Docmost sign-in.
Create the workspace owner privately. Connect SMTP before using email
invitations and password resets.

## Write Your First Page

> **Ask your AI agent:** Help me create a team handbook, attach a sample file, and check that my changes are saved.

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



Create a page in a Space, write some notes, and attach a file. Reload the page
and retrieve the attachment. Keep the bucket private; Docmost checks access
when serving the file.

![Docmost showing a team handbook with a saved file attachment.](/assets/images/guides/docmost/wiki.png)

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

Create a prebuilt-image Environment, then create and link PostgreSQL and Redis:

    blossom app:create --data app.yml
    blossom environment:create --data environment.yml
    blossom database_instance:create --data postgres.yml --follow
    blossom cache_instance:create --data redis.yml --follow
    blossom environment_link:create --data database-link.yml
    blossom environment_link:create --data redis-link.yml
    blossom env_var:push --environment environment-100 --file .env.production
    blossom service:create --data docmost-service.yml
    blossom environment:deploy --id environment-100 --follow

Set a strong, stable `APP_SECRET` and the correct `APP_URL`. Use the linked
`DATABASE_URL` and `REDIS_URL`, with a non-evicting Redis configuration for jobs.
Set `STORAGE_DRIVER=s3` and the documented `AWS_S3_*` bucket, endpoint, region,
and credential settings. R2 uses its S3 API endpoint, region `auto`, and
path-style addressing.

Inspect the selected image's actual runtime. Hardened releases may have no
shell or curl: start Node directly and use a Node-based command probe for
`/api/health`. When deriving the public URL from `BLOSSOM_SERVICE_URL`, do so
in Node without adding a shell dependency. Preserve WebSocket routing for the
real-time editor.

Allow the release's supported database migrations to finish before serving
requests. Keep one application instance for this recipe and wait for each
step of a stop-before-start update:

    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

</details>

## Keep Your Wiki Through Updates

> **Ask your AI agent:** Update Docmost and check that my workspace, pages, and attachments remain.

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



Preserve PostgreSQL, Redis, the bucket, and `APP_SECRET`. Stop the old
application before starting its replacement; this update path has a short
outage. External storage alone does not establish multi-Container support.

Sign in again, open a saved page, and retrieve its attachment. Add another edit
to check that the replacement can still save through the real-time editor.

## What You Get

- A private team wiki with a real-time editor
- Pages and workspace records in managed PostgreSQL
- Attachments in your private bucket
- Saved content that survives application Container replacement
