This repo has the necessary setup for running jquery-wp-content in WordPress locally using Docker.

1. Clone this repo and its submodules

git clone --recursive git@github.com:jquery/jquery-wp-docker.git

2. Copy the wp-config-sample.php file to wp-config.php

cp wp-config-sample.php wp-config.php

3. Edit the wp-config.php file and set unique keys and salts using https://api.wordpress.org/secret-key/1.1/salt/. Do NOT change the DB_ defines.

define('AUTH_KEY',         'put your unique phrase here');
define('SECURE_AUTH_KEY',  'put your unique phrase here');
// etc.

4. Copy .env.example to .env and edit the file to define database credentials

cp .env.example .env

5. Optionally, add local SSL certs to the ssl directory.

   • If you don't have any, you can generate them using mkcert. Run the following:

     mkcert -install

   • Then, in the ssl directory, run:

     mkcert \
     local.jquery.com \
     local.api.jquery.com \
     local.blog.jquery.com \
     local.learn.jquery.com \
     local.releases.jquery.com \
     local.jqueryui.com \
     local.api.jqueryui.com \
     local.blog.jqueryui.com \
     local.jquerymobile.com \
     local.api.jquerymobile.com \
     local.blog.jquerymobile.com \
     local.jquery.org \
     local.brand.jquery.org \
     local.contribute.jquery.org \
     local.meetings.jquery.org

     Wildcards don't work for multi-level subdomains. Add each site to the list of domains.

   • Rename the created certs to cert.pem and cert-key.pem.

6. Run docker compose up --build to start the containers.

7. Import the database from a production WordPress instance.

# You need SSH admin access to this production server
ssh wp-05.ops.jquery.net
sudo -u tarsnap mysqldump --databases `sudo -u tarsnap mysql -B -N -e "SHOW DATABASES LIKE 'wordpress_%'"` > wordpress.sql

Then, on your local machine, run:

# Copy the SQL dump from your home directory on the server (as created by the previous command)
scp wp-05.ops.jquery.net:~/wordpress.sql .
# Docker root database password must match your .env file
# NOTE: There must be no space between -p and the password!
docker exec -i jquerydb mysql -u root -proot < wordpress.sql

8. Visit http://local.api.jquery.com, or https://local.api.jquery.com if you created certs.

To update your setup after pulling down changes, run:

docker compose down
docker compose up --build -d

To open a REPL to the database, run the mysql CLI in the jquerydb container. Make sure to include the -i and -t opens to connect your own shell to the shell in the container.

docker exec -it jquerydb mysql -u root -proot

jquery-wp-docker is set up to use ports 80 and 443 by default so no extra work is needed to support SSL. However, if either port is in use on your host, you can create a .env file in this directory and set the following environment variable with a port number of your own choosing:

JQUERY_WP_HTTP_PORT=8080

Then, visit the port directly when visiting sites, e.g. http://local.api.jquery.com:4000.

443 is only spun up by Apache if certs are available in the /ssl folder. However, the docker-compose.yml does still expose port 443 to the docker images's 443, even if nothing is listening on that port. This shouldn't be an issue in most cases, but the port can be changed in the .env. file to avoid any conflicts.

JQUERY_WP_HTTPS_PORT=0

You do not need to configure your /etc/hosts file to define local.jquery.com, because we have defined these domains in the production DNS for jquery.com as alias for localhost. However, if you plan to work offline, you can add the following rules:

127.0.0.1 local.jquery.com
127.0.0.1 local.api.jquery.com
127.0.0.1 local.blog.jquery.com
127.0.0.1 local.learn.jquery.com
127.0.0.1 local.releases.jquery.com

127.0.0.1 local.jqueryui.com
127.0.0.1 local.api.jqueryui.com
127.0.0.1 local.blog.jqueryui.com

127.0.0.1 local.jquerymobile.com
127.0.0.1 local.api.jquerymobile.com
127.0.0.1 local.blog.jquerymobile.com

127.0.0.1 local.jquery.org
127.0.0.1 local.brand.jquery.org
127.0.0.1 local.contribute.jquery.org
127.0.0.1 local.meetings.jquery.org