Directus with Docker lets you run a self-hosted headless CMS that turns a SQL database into a content management system and an auto-generated API. You can install Directus manually with Docker Compose or deploy it faster using Hostinger’s Directus Docker template.<\/p>
To set up Directus, you’ll need a server or local machine with Docker, Docker Compose, persistent storage, and a secure secret key. After installation, you can open Directus Studio, create collections, manage content visually, and expose selected data through REST or GraphQL endpoints for your website, app, or internal tool.<\/p>
Before installing Directus with Docker<\/a>, make sure you have:<\/p> Installing Directus with Docker lets you run the headless CMS in an isolated container with its required runtime, configuration, and dependencies. The fastest setup uses the official directus\/directus Docker image, while the recommended setup uses Docker Compose with persistent storage for the database, uploads, and extensions.<\/p> Directus requires Docker to be installed on your server<\/a>. Check your Docker version with:<\/p> Then check whether Docker Compose<\/a> is available:<\/p> If both commands return version numbers, you can continue with the installation.<\/p> Create a new directory for your Directus project. This directory will store the Docker Compose file and the folders Directus needs to keep data after the container restarts.<\/p> The database folder stores the SQLite database file, uploads stores media files, and extensions stores custom Directus extensions.<\/p> Create a docker-compose.yml file inside the directus directory:<\/p> Add the following configuration:<\/p> This configuration starts Directus on port 8055, stores Directus data outside the container, and uses SQLite as the database engine. SQLite is suitable for testing, small projects, and local development. For production websites or applications, use PostgreSQL or MySQL instead.<\/p> Replace replace-this-with-a-long-random-value with a secure secret. Directus uses this value to sign access tokens, so don’t reuse simple passwords or public strings.<\/p> Run the following command from the same directory as your docker-compose.yml file:<\/p> The -d option runs Directus in detached mode, so the container keeps running in the background.<\/p> Check whether the container is active:<\/p> You should see a running container based on the directus\/directus image.<\/p> Open Directus in your browser using your server IP address or local machine address:<\/p> If you installed Directus on a VPS, use:<\/p> Directus will show the onboarding screen on first launch. Create your first admin account by entering your email, password, and project details.<\/p> After creating the admin account, test the Directus server with the \/server\/ping endpoint:<\/p> A working Directus instance returns:<\/p> You can also check the container logs if the page doesn’t load:<\/p> To stop the Directus container, run:<\/p> To start it again, run:<\/p> Because the Compose file mounts the database, uploads, and extensions folders as volumes, your Directus project data remains available after restarting the container.<\/p> Hostinger’s Docker catalog<\/a> lets you deploy Directus on a VPS without manually pulling the Docker image, creating a Docker Compose file, or configuring the container from scratch. This option is best if you want a faster way to launch a self-hosted headless CMS and start building a database-backed API.<\/p> To deploy Directus with Hostinger’s Docker template:<\/p> After deployment, Directus runs as a Docker application on your VPS. You can use Hostinger’s Docker manager to check the container status, view logs, and manage updates without setting up the container manually through the command line.<\/p> Open your Directus instance in the browser using the access URL provided in hPanel. If you’re using the server IP address directly, the URL usually follows this format:<\/p> To check whether Directus is responding, open the server ping endpoint:<\/p> A working Directus instance returns:<\/p>\n
How to install Directus with Docker<\/h2>
1. Check that Docker is installed<\/h3>
docker --version<\/pre>
docker compose version<\/pre>
2. Create a Directus project directory<\/h3>
mkdir directus\ncd directus\nmkdir database uploads extensions<\/pre>
3. Create a Docker Compose file<\/h3>
nano docker-compose.yml<\/pre>
services:\ndirectus:\nimage: directus\/directus:11.17.0\nports:\n- 8055:8055\nvolumes:\n- .\/database:\/directus\/database\n- .\/uploads:\/directus\/uploads\n- .\/extensions:\/directus\/extensions\nenvironment:\nSECRET: \"replace-this-with-a-long-random-value\"\nDB_CLIENT: \"sqlite3\"\nDB_FILENAME: \"\/directus\/database\/data.db\"\nWEBSOCKETS_ENABLED: \"true\"<\/pre>
4. Start the Directus container<\/h3>
docker compose up -d<\/pre>
docker ps<\/pre>
5. Open the Directus setup screen<\/h3>
http:\/\/localhost:8055<\/pre>
http:\/\/your-server-ip:8055<\/pre>
6. Verify that Directus is running<\/h3>
http:\/\/your-server-ip:8055\/server\/ping<\/pre>
pong<\/pre>
docker compose logs directus<\/pre>
7. Stop or restart Directus<\/h3>
docker compose down<\/pre>
docker compose up -d<\/pre>
How to deploy Directus with Hostinger’s Docker template<\/h2>
\n
http:\/\/your-server-ip:8055<\/pre>
http:\/\/your-server-ip:8055\/server\/ping<\/pre>
pong<\/pre>