Bobcares

Headless WordPress Docker Compose | Setup Guide

by | Feb 29, 2024

Learn how to set up Headless WordPress with Docker Compose & Docker. Our WordPress Support team is here to help you with your questions and concerns.

Headless WordPress Docker Compose

Did you know that a headless WordPress site is a WordPress installation that is decoupled from the front end?

It lets developers use any front-end technology, like React or Vue.

Today, we will take a closer look at setting up a headless WordPress site locally using Docker and docker-compose, and then integrating it with a NextJS application.

Setting Up a Headless WordPress Site with Docker

To get started, we need Docker and docker-compose. Docker is a containerization platform, while docker-compose is a tool for defining and running multi-container Docker applications.

Now, we have to create a docker-compose.yml file with configurations for MySQL and WordPress services. This file will define the containers, their dependencies, and environment variables.

Headless WordPress Docker Compose

 

This docker-compose file sets up a MySQL database and a WordPress container. We can adjust the environment variables as needed. To start the containers, head to the directory with the docker-compose.yml file and run the command `docker-compose up -d`.

We can access our WordPress site at http://localhost:8000.

How to Use Docker for Local Development with NextJS

Now, it is time to integrate the headless WordPress site with a NextJS application.

  1. We start by creating a Next app using the WordPress preset:

    yarn create next-app --example cms-wordpress cms-wordpress-app

  2. Then, set up a local WordPress site with minimal configuration via @wordpress/wp-env.
  3. Next, install the package:

    yarn add @wordpress/env

  4. We can create a .wp-env.json config file for the local Docker site:

    .wp-env.json config file

  5. We can make sure the WordPress site is working by running:

    yarn wordpress

  6. Then, configure NextJS to work with WordPress by creating a .env file:

    WORDPRESS_API_URL=http://localhost:4113/graphql

  7. Now, start the NextJS application:

    yarn && yarn dev

    Our NextJS front-end should be accessible at http://localhost:3000/.

Furthermore, we can add a plugin or mu-plugin for custom code. This involves creating a directory named “wordpress-plugin” and adding a file inside it. We have to update the “plugins” section of .wp-config.json to include this directory:

update the "plugins" section of .wp-config.json

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to set up Headless WordPress with Docker Compose & Docker.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF