For local development:
cp htaccess-local .htaccess
On your server:
cp htaccess-remote .htaccess(this version has more security settings)cp wp-config-sample.php wp-config.php. Then update the database values to match what you have configured with your web host AND fill in the unique keys and salts (generate these). It's also a good idea to change the table prefix fromwp_to something unique.
docker-compose up -d
This creates four docker containers:
- MySQL database
- Wordpress Container (php/apache)
- NPM Container (install javascript dependencies, and task run for the default theme)
- Composer Container (installing wordpress plugins & wordpress itself which is version controlled via composer)
If you update the package.json file you have to rebuild the images docker-compose build.
To prepare for deploying:
docker run -i -t -v $(pwd)/.:/deploy -w="/deploy" wordpress_npm npm run build
This runs the build command in package.json within a temporary container built from the wordpress_npm image.
This current setup uses rsync via deploy.sh.
Update the deploy.sh file by changing USERNAME, DOMAIN, and FOLDER to match your remote server's information. Then you can run sh deploy.sh.
Add the plugins to composer.json (search for the here); a few are in there already as examples.
Host: 0.0.0.0
Port: 32769 or something similar.
Make sure you check the actual port as it can be different everytime. docker ps -a.
docker rm -fv $(docker ps -aq)
If you don't have a use for a custom theme that has a dev workflow run on NPM and Gulp, you can remove the "npm" entry in docker-compose.yml. You can also remove gulpfile.js, package.json and the whole default theme directory.
docker run -i -t -v $(pwd)/.:/var/www/html -w="/var/www/html" wordpress_npm npm run build
- Add details on remote server configuration.
- Include steps on deploying (via rsync to start).
- Remove gulp (or make it more agnostic to the setup).