Skip to content

A Docker WordPress Local Environment with HTTPS & LDAP

Notifications You must be signed in to change notification settings

ucsc/wp-dev.ucsc

Repository files navigation

Docker Environment for UCSC WordPress theme and plugins

Prerequisites

  1. The instructions assume you have git and Docker installed. Have the docker app open while going through the steps.
  2. You need a UCSC VPN connection to use the Campus Directory block in the UCSC Gutenberg Blocks plugin.

Setup

  1. Go to your terminal and run this command to clone this repo

    • git clone https://github.com/ucsc/wp-dev.ucsc.git
    • cd into the folder cd wp-dev.ucsc
  2. Edit your hosts file by running sudo nano /etc/hosts in your terminal and add 127.0.0.1 wp-dev.ucsc

    • On Mac OS do ctrl+O to writeout and hit enter on your keyboard
    • Then hit ctrl+X to exit
    • You have now successfully edited you host file.
  3. Change .env.example.txt to .env by following these steps:

    • cd into the folder cd wp-dev.ucsc if you are not in it already
    • Run the command ls -a to see hidden files and verify there is a file called .env.example.txt
    • Run this command to change the name to .env mv .env.example.txt .env
    • Run ls -a to verify the name of the file has changed to .env
  4. In the wp-dev.ucsc directory build and start the WordPress server with HTTPS & PHP LDAP module (Allow time for this command to finish)

    • docker compose up -d
    • Once this is finished running you should have a total of 5 docker containers up and running. You can verify this by opening up the docker app and making sure there is a green dot next to each container.
    • Troubleshooting: If there is not a green dot next to each container then here is what you should do: select all the containers in your docker app and delete them all. Once all the containers have been deleted go to your terminal in the wp-dev.ucsc directory and run docker compose up -d again. This should solve the issue and have all 5 containers up and running succesfully.

Important

Check that a wp-config.php file exists in the ./public/ folder before proceeding

  1. Run the following script to clone the theme and plugins to the correct project directories.

    • ./setup.sh
  2. Next we install WordPress, activate the theme & plugin, run composer install on the theme as well as npm install on both the plugin and the theme

    • docker compose -f docker-compose-install.yml run theme_composer_install
    • docker compose -f docker-compose-install.yml run theme_npm_install
    • docker compose -f docker-compose-install.yml run plugin_npm_install (may take up to 2 minutes to complete)
    • docker compose -f docker-compose-install.yml run wordpress_install

Your installation is now complete.

Troubleshooting: If there is not a green dot next to each container then here is what you should do: select all the containers in your docker app and delete them all. Once all the containers have been deleted go to your terminal in the wp-dev.ucsc directory and run docker compose up -d again. This should solve the issue and have all 5 containers up and running succesfully.

Running the Docker services for development

Now that WordPress is installed and the plugins and theme are built, we can start watching for changes to code and rebuild when necessary

  • Starts the WordPress server environment
    • docker compose up -d
  • Starts the Node development environments for the theme and blocks plugin
    • docker compose -f docker-compose-start.yml up -d

Tip

Swap up with down in the commands above to stop your containers. You must run both commands to start and stop the development environments.

In Your Browser

At this point you should be able to visit https://wp-dev.ucsc/wp-admin in a browser. In Google Chrome you will get a error saying "Your connection is not private", this is due to the local certificates. You can click Advanced -> proceed to wp-dev.ucsc. To login:

  • username: admin
  • password password

Tip

  • You can run WP-CLI commands with docker exec ${NAME}-cli wp <COMMAND>
  • ${NAME} is what you used in your .env file

VScode/Xdebug setup

The PHP Debug plugin is required. On the debug tab click Create a launch.json file and select type php.

You can replace the contents of launch.json with the following:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Listen for Xdebug",
      "type": "php",
      "request": "launch",
      "port": 9003,
      "pathMappings": {
        "/var/www/html/wp-content/plugins/ucsc-gutenberg-blocks": "${workspaceRoot}"
      },
      "hostname": "wp-dev.ucsc"
    }
  ]
}

About

A Docker WordPress Local Environment with HTTPS & LDAP

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •