Skip to content

imranhsayed/nextjs-headless-wordpress

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🎨 Next.js Headless WordPress

Project Status: Active. Stars Forks Contributors Follow

  • Headless WordPress, using Decoupled Architecture in Next.js
  • Backend in WordPress.
  • Front end in React

Run this from root

docker-compose -f backend/docker-compose.yml up -d 
  • Make sure to set Home Page as Front page from WordPress dashboard > Customize > Homepage Settings. WordPress Backend will be available on http:https://localhost:8020

phpMyAdmin: You can access php myadmin on http:https://localhost:8183

port: mysql:3306
username: root
password: root

phpmyadmin docker image already comes with the username root and we have set the mysql password in the dockerfile

  • If you happen to use your own WordPress setup, be sure to install and activate plugins from composer.json and add your own WordPress site URL in an .env file, You can check the .env-example file for reference.

Run this from root for the first time.

cd frontend; npm i && npm run dev

During development

cd frontend; npm run dev

Frontend will be available on port http:https://localhost:3000

Evironment vars.

Create a .env file taking reference from .env-example inside frontend directory and add your WordPress Site URL ( for local development put http:https://localhost:8020 as your WordPress URL)

Development ( Developers only )

  1. When we change the composer.json, run from root
docker-compose -f backend/docker-compose.yml down && \
docker-compose -f backend/docker-compose.yml up -d 

First line command will stops and removes all the docker containers and second line command will restart all containers. Notice that -d is to run in detach mode and you can always remove that flag, and run the command so you can see the live logs. Or you can check the logs for

  1. Check the logs While the above command is running in detached mode ( -d ), you can run this command in a new terminal tab to see the live logs.
docker logs -f container-name
  1. Login to SSH and wp cli.
docker exec -it image-name bash // e.g. docker exec -it backend_wordpress_1 bash
wp

e.g.

docker container ls

result

CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS              PORTS                  NAMES
d0b4a3b0074f        wordpress:latest    "docker-entrypoint.s…"   About a minute ago   Up About a minute   0.0.0.0:8000->80/tcp   backend_wordpress_1
aad078ebe131        mysql:5.7           "docker-entrypoint.s…"   About a minute ago   Up About a minute   3306/tcp, 33060/tcp    backend_db_1

Here container-name is backend_db_1 or backend_wordpress_1

  1. If you make changes to docker-compose.yml file, run the following:

If you happend to change the port in docker-compose.yml make sure to delete the db directory and then run below.

docker-compose -f backend/docker-compose.yml down && \
docker-compose -f backend/docker-compose.yml up -d

Debugging

  1. If you get 404 on frontend for graphql request, check to see that the .htaccess file in wordpress directory has the rules
# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

References for Docker Images.

  1. phpMyAdmin