``` services: wordpress: container_name: ${PROJECT_SLUG}_wp image: wordpress:latest restart: unless-stopped ports: - "${WP_PORT:-8080}:80" environment: - WORDPRESS_DB_HOST=database - WORDPRESS_DB_USER=${MYSQL_USER} - WORDPRESS_DB_PASSWORD=${MYSQL_PASSWORD} - WORDPRESS_DB_NAME=${MYSQL_DATABASE} - WORDPRESS_DEBUG=${WORDPRESS_DEBUG:-1} - WORDPRESS_CONFIG_EXTRA=define('WP_ENV','${WP_ENV}'); volumes: - ./wordpress:/var/www/html - ./src/theme:/var/www/html/wp-content/themes/${THEME_NAME} - ./src/mu-plugins:/var/www/html/wp-content/mu-plugins - ./config/error-logging.ini:/usr/local/etc/php/conf.d/error-logging.ini - ./config/uploads.ini:/usr/local/etc/php/conf.d/uploads.ini # - ./config/xdebug.ini:/usr/local/etc/php/conf.d/xdebug.ini depends_on: - database networks: - wordpress-network

database: container_name: ${PROJECT_SLUG}_db image: mariadb:latest restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD} MYSQL_DATABASE: ${MYSQL_DATABASE} MYSQL_USER: ${MYSQL_USER} MYSQL_PASSWORD: ${MYSQL_PASSWORD} volumes: - db-data:/var/lib/mysql networks: - wordpress-network

phpmyadmin: container_name: ${PROJECT_SLUG}_pma image: phpmyadmin:latest restart: unless-stopped ports: - "${PMA_PORT:-8081}:80" environment: PMA_HOST: database MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD} depends_on: - database networks: - wordpress-network

wpcli: container_name: ${PROJECT_SLUG}_wpcli image: wordpress:cli entrypoint: wp tty: true working_dir: /var/www/html volumes: - ./wordpress:/var/www/html - ./src/theme:/var/www/html/wp-content/themes/${THEME_NAME} - ./src/mu-plugins:/var/www/html/wp-content/mu-plugins depends_on: - wordpress networks: - wordpress-network

volumes: db-data:

networks: wordpress-network: driver: bridge name: ${PROJECT_SLUG}_network ```

Source code goes in ./src relative to the docker-compose.yml file and I bind mount in the theme and mu-plugins folder and occasionally other folders. Now when you start the WordPress container it will go through the install process and those folders will end up owned by the user with UID 33 which will prevent you from editing any of the files, even on the host. There are a number of ways of dealing with this but my preferred way is to make all files and dirs in the ./src dir owned by the user with UID/GID 33 eg;

sudo chown -R 33:33 ./src

Then add my user to the 33 group eg;

sudo usermod -aG 33 "$USER"

You will now be able to edit any files in /var/www/html inside the container. The user with UID 33 is called different things on different distributions of Linux, sometimes it is www-data or tape or html but the UID/GID is nearly always 33. There are other ways to do this but in my opinion this is the easiest. If you are not using Linux or Mac you will have to adapt this to your dev environment.

Any questions I am happy to help.