Are Postgres and Redis not recommended for use with Directus anymore?

Help
1

Hi everyone,

I noticed that the official docker-compose.yml example on the Directus website was recently changed (a few days ago). The previous version included PostgreSQL and Redis in the configuration, but the current version now uses SQLite instead.

Here’s the current recommended setup:

services:
    directus:
        image: directus/directus:11.5.1
        ports:
            - 8055:8055
        volumes:
            - ./database:/directus/database
            - ./uploads:/directus/uploads
            - ./extensions:/directus/extensions
        environment:
            SECRET: "replace-with-random-value"
            ADMIN_EMAIL: "admin@example.com"
            ADMIN_PASSWORD: "d1r3ctu5"
            DB_CLIENT: "sqlite3"
            DB_FILENAME: "/directus/database/data.db"
            WEBSOCKETS_ENABLED: "true"

I’m wondering what this change means:

  • Does this mean PostgreSQL and Redis are no longer recommended for production use with Directus?

  • Is SQLite now the preferred database option?

  • What about Redis for caching - is it still recommended, or is it no longer necessary?

I’m planning a production deployment and want to make sure I’m following current best practices. Any clarification would be greatly appreciated!

Thanks!

2

Hi @dersaei! Welcome to the community :slight_smile:

For production usage I’d most definitely still rely on Postgres and Redis. The simplified version you’ve copied here is just for quick local testing and evaluation purposes. It’s the quickest way from 0 to having a Directus instance you can experiment with.

Outside of Redis + Postgres, I’d also highly recommend running multiple containers of Directus itself for scaling and high availability using something like Kubernetes or a platform-as-a-service provider.

I’ll make note on my end to update that doc so it’s clearer that that’s just a quick getting started and not a full production example :flexed_biceps: