Directus Production Deployment with Docker: Step-by-Step Guide

Imagine: you deployed Directus via npx, quickly got an admin panel, but a month later, with increased traffic, the site went down due to lack of caching — and media files were lost on disk failure. It's exactly these situations that push you toward a production deployment with Docker, PostgreSQL, and S3. This article provides a proven setup template that we use in numerous projects, from corporate portals to high-load APIs. Directus is a headless CMS that provides REST and GraphQL APIs on the fly, without generation. According to tests, API response speed is 2–3 times higher than Strapi, thanks to the lack of ORM layers. For production we always use Docker — it guarantees isolation, reproducibility, and easy scaling.

Why Choose Directus for Production?

Directus is not just another CMS. It is a headless platform that provides REST and GraphQL APIs on the fly, without generation. You integrate it into any existing database — no data migration needed. According to reviews, development speed doubles compared to traditional CMS. We recently deployed Directus for a large online store with a catalog of 50,000 products. After migrating from WordPress to Directus, the catalog page load time dropped from 3 seconds to 400 ms thanks to Redis caching and SSR on Nuxt 3. That is a real example: API speed increased 3 times, and infrastructure costs decreased by abandoning the monolith. Get an engineer consultation on choosing a headless CMS for your project.

How to Deploy Directus to Production with Docker?

The process includes five mandatory steps:

1. Task audit — determine load, content volume, API requirements.
2. Stack selection — Docker + PostgreSQL + S3 (or Cloudflare R2 for cheap storage).
3. Deployment — write docker-compose.yml, configure Redis for caching, connect CDN.
4. Environment configuration — SECRET, CORS, email, storage variables.
5. Turnkey handover — documentation, credentials, team training.

Quick Start: via npx

npx create-directus-project@latest my-directus

# Questions:
# Database: PostgreSQL
# Host: localhost
# Port: 5432
# Database name: directus
# Username: directus
# Password: ...
# Admin email: [email protected]
# Admin password: ...

cd my-directus
npx directus start

This method is suitable for development, but not for production — no isolation, hard to scale.

Docker Deployment (Recommended)

Example ready docker-compose.yml:

version: '3'
services:
  directus:
    image: directus/directus:10.latest
    restart: unless-stopped
    ports:
      - "8055:8055"
    volumes:
      - ./uploads:/directus/uploads
      - ./extensions:/directus/extensions
    environment:
      SECRET: ${SECRET}
      DB_CLIENT: pg
      DB_HOST: postgres
      DB_PORT: 5432
      DB_DATABASE: ${DB_NAME}
      DB_USER: ${DB_USER}
      DB_PASSWORD: ${DB_PASSWORD}
      ADMIN_EMAIL: ${ADMIN_EMAIL}
      ADMIN_PASSWORD: ${ADMIN_PASSWORD}
      PUBLIC_URL: https://cms.example.com
      CORS_ENABLED: true
      CORS_ORIGIN: https://example.com
      CACHE_ENABLED: true
      CACHE_STORE: redis
      REDIS_HOST: redis
      REDIS_PORT: 6379
      STORAGE_LOCATIONS: local
      STORAGE_LOCAL_DRIVER: local
      STORAGE_LOCAL_ROOT: /directus/uploads
    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:15-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: ${DB_NAME}
      POSTGRES_USER: ${DB_USER}
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    volumes:
      - postgres_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ${DB_USER}"]
      interval: 10s

  redis:
    image: redis:alpine
    restart: unless-stopped

volumes:
  postgres_data:

How to Configure Storage and Cache?

S3 Storage

For production, always use external storage. Example variables:

STORAGE_LOCATIONS=s3
STORAGE_S3_DRIVER=s3
STORAGE_S3_KEY=ACCESS_KEY
STORAGE_S3_SECRET=SECRET_KEY
STORAGE_S3_BUCKET=my-bucket
STORAGE_S3_REGION=eu-west-1
STORAGE_S3_ENDPOINT=https://s3.amazonaws.com
# For Cloudflare R2:
# STORAGE_S3_ENDPOINT=https://<account-id>.r2.cloudflarestorage.com
# STORAGE_S3_REGION=auto

Storage Comparison:

Order custom storage setup — we will choose the optimal option for your project.

Caching with Redis

Redis is mandatory for production: cache reduces database load by 60–80%. The configuration is already included in docker-compose.yml. Additionally, you can set CACHE_TTL (default 5 minutes). For high loads, use Redis Cluster. The cluster requires multiple nodes — this provides horizontal scaling and fault tolerance.

What Problems Does Directus Solve?

Directus solves the problem of connecting backend to frontend by providing a flexible API. It is especially useful when you need to quickly launch a product with custom data structures. For example, for a marketplace with different product types, you don't need to write separate controllers — Directus generates endpoints automatically.

Common Directus Installation Mistakes

• Using npm without Docker — issues with scaling and updates.
• Skipping CORS configuration — CORS errors on frontend.
• Storing media in local filesystem — data loss on disk failure.
• No caching — slow API response at 100+ requests per second.
• Incorrect SECRET generation — vulnerability to CSRF attacks.
• No monitoring — performance issues go unnoticed.

What's Included in the Directus Setup Service?

As part of the service, you receive:

• Fully configured production stack: Docker, PostgreSQL, Redis, S3.
• Configuration tailored to your load (load balancing, CDN).
• Deployment and maintenance documentation.
• Admin panel access, API tokens.
• Team training (2 hours online).
• 2 weeks of support after launch.

This set covers 90% of typical projects. For non-standard ones, individual audit.

Timelines and Cost

Basic setup with Docker, PostgreSQL, S3, and basic configuration takes 2 to 4 hours. Complex projects (custom extensions, SSO, data migration) take 1 to 5 days. Cost is determined individually after audit. Get an engineer consultation — we'll evaluate your project in 1 day. Contact us to discuss details.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.