From Wordpress to Directus, but on what server/domain?

Help
2

Hey there @Criss

Great question, and welcome to the Directus community.

To answer your points step-by-step:

Where to install Directus

Since your current live site is running on WordPress, the best approach right now is to install Directus on a subdomain, for example: admin.yourdomain.com

This keeps your live WordPress site untouched while you build and experiment with Directus in the background.
Later, when your new frontend is ready, you can easily switch your main domain (yourdomain.com) to point to the new frontend while keeping Directus running on the subdomain (which acts as your headless CMS backend).

Tip: Most production setups keep Directus on a subdomain even after launch, since it’s not meant to be public-facing.

About Docker and cPanel

Your hosting provider is correct — Docker isn’t officially supported on cPanel-managed servers, because cPanel controls Apache, ports, and networking.
If you want to use Docker (which is the easiest way to deploy and manage Directus), you’ll need a VPS or cloud instance without cPanel (for example, on DigitalOcean, Hetzner, or AWS).

If your current VPS has cPanel, you can:

  • Either install Directus without Docker (manually using Node.js, npm, and a database like MySQL/PostgreSQL).
  • Or get a separate small VPS just for Directus, which is often the cleaner option.

Migration later

Yes, it’s absolutely possible to migrate later from one server to another (even from a non-cPanel VPS to a cPanel VPS or vice versa).
Directus is just a Node.js app with a database — so migration typically involves:

  1. Exporting/importing your database.
  2. Copying your /uploads (or storage) folder.
  3. Copying your .env file and reinstalling dependencies.

That’s it. As long as your database and storage are backed up, you can move Directus anywhere.

In short

  • Install Directus on a subdomain (e.g., admin.yourdomain.com).
  • Avoid cPanel if you plan to use Docker.
  • Migration between servers is straightforward later.
  • Your live WordPress site stays safe while you build your new backend.