Solves weird permission issues in wp-content.

.gitignore

@@ -1 +1,4 @@
 .env
+docker-compose.yml
+default.conf
+wp-config.php

Dockerfile.wordpress_fpm

@@ -1,7 +1,8 @@
 # Wordpress - make a copy of wp-includes to compare with existing volumes
 
 # 'docker-compose exec wordpress bash -c 'cd /var/www/html/wp-includes && grep wp_version version.php'
-FROM wordpress:6-fpm
+ARG WORDPRESS_VERSION=user-defined
+FROM wordpress:${WORDPRESS_VERSION}
 
 # ancient debian
 #RUN apt update && apt -y install vim less 

README.md

@@ -1,31 +1,30 @@
 # ComposePress  
 
-A Docker-based toolkit that streamlines WordPress upgrades using official images. Provides pre-configured docker-compose files, Dockerfiles, and standardized procedures to make WordPress maintenance more predictable and reliable.
+ComposePress is a **Docker-based toolkit** designed to streamline WordPress upgrades using official images. It provides **pre-configured Docker Compose files**, Dockerfiles, and standardized procedures to make WordPress maintenance more predictable and reliable.  
 
-## Project Configuration
+---
 
-### Project Name
+## 🚀 Project Configuration  
-This project requires a project name, which should be defined in an `.env` file:
+
+### **Project Name & WordPress Version**  
+Define a **unique project name** and **WordPress version** in the `.env` file:  
 ```bash
 COMPOSE_PROJECT_NAME=test
+WORDPRESS_VERSION=6-fpm
 ```
 
-### Database Host Configuration
+---
-To avoid conflicts, use the following format for the database host:
-```bash
-WORDPRESS_DB_HOST=${COMPOSE_PROJECT_NAME}-database-1:3306
-```
 
-## Environment Variables
+## 🛠 Environment Variables  
 
-### Docker Images
+### **Docker Images**  
 ```bash
-# Web and Database Images
+# Web & Database Images
 IMAGE_WEB=test_web_staging
 IMAGE_DATABASE=mariadb:11.5
 ```
 
-### Let's Encrypt Configuration
+### **Let's Encrypt Configuration**  
 ```bash
 VIRTUAL_HOST=test.test.org
 LETSENCRYPT_HOST=test.test.org
@@ -33,73 +32,164 @@ LETSENCRYPT_EMAIL=test@test.com
 LETSENCRYPT_TEST=true
 ```
 
-### Database Configuration
+### **Database Configuration**  
 ```bash
-WORDPRESS_DB_HOST=${COMPOSE_PROJECT_NAME}-database-1:3306
+WORDPRESS_DB_PASSWORD=wordpress # Used for MYSQL_PASSWORD AND MYSQL_ROOT_PASSWORD
-WORDPRESS_DB_PASSWORD=wordpress
-MYSQL_ROOT_PASSWORD=wordpress
 MYSQL_DATABASE=wordpress
 MYSQL_USER=wordpress
-MYSQL_PASSWORD=wordpress
+TABLE_PREFIX=test # optional
 ```
 
-### Volume Configuration
+### **Volume Configuration**  
 ```bash
-# External Volumes
+# External Volumes (Persist Data)
 DB_VOLUME=test_db_staging
 CONTENT_VOLUME=test_content_staging
 
-# Recreated Volumes
+# Recreated Volumes (Rebuild On Setup)
 HTML_VOLUME=test_html_staging
 ```
 
-## Usage
+---
 
-### Upgrade Process
+## 📂 Configuration Files  
 
-1. Stop the current containers and remove volumes:
+Three important configuration files are available in the project directory:  
 ```bash
-docker compose down -v
+Nginx (after editing, perform a restart):
+
+./default.conf  # generate-compose-nginx.sh respects user added changes
+./nginx.conf    # Manually customizable configuration
+
+Wordress:
+
+./wp-config.php # generated once by generate-compose-nginx.sh and respects user added changes
+
 ```
 
-2. Update WordPress version:
+---
-   - Modify version in `Dockerfile.wordpress_fpm`
-   - Update `IMAGE_WEB` in `.env` file
 
-3. Build and test the new environment:
+## 🚀 Usage  
+
+### **Initialize a Project with a Unique `COMPOSE_PROJECT_NAME`; expects one word**  
+Run the following script to generate the required files:  
 ```bash
-# Build initial configuration
+./generate-compose-nginx.sh
+```
+
+---
+
+## 🔄 Upgrade Process
+
+
+### 🚀 **Automated Upgrade (Recommended)**  
+If you want a **fully automated** upgrade, use the `wp-rocket-launch.sh` script:  
+```bash
+./wp-rocket-launch.sh
+```
+
+✅ Automatically cleans up existing containers and volumes  
+✅ Builds the custom WordPress image   
+✅ Deploys the new version with minimal manual intervention   
+✅ Copies new installation files to production and correct permissions 
+✅ Wordpress salt keys are shuffled   
+
+Alternatively, follow the manual upgrade process below.
+
+
+### 🚀 **Manual Upgrade (Expert Mode)** 
+
+### **1️⃣ Stop Containers & Clean Up**  
+```bash
+docker compose down -v
+
+# Optional: Remove external database & content volume (DANGER: Only do this if you have backups)
+grep -E 'DB_VOLUME|CONTENT_VOLUME' .env | cut -d '=' -f2 | xargs -I {} sh -c 'docker volume rm {} 2>/dev/null; docker volume create {}'
+
+# Optional: Remove WordPress Image
+docker rmi $(grep IMAGE_WEB .env | cut -d '=' -f2)
+```
+
+### **2️⃣ Update WordPress Version**  
+Modify the version in .env:  
+```bash
+WORDPRESS_VERSION=7-fpm
+```
+
+### **3️⃣ Build & Deploy**  
+```bash
+# Build custom WordPress image
 docker compose -f docker-compose.first.yml build 
 
-# Test the build
+# Install or upgrade WordPress volume from custom image
 docker compose -f docker-compose.first.yml up -d
 
-# Stop test environment
+# Stop WordPress container (but keep HTML volume)
 docker compose -f docker-compose.first.yml down
 
 # Start production environment
 docker compose up -d
 ```
 
-4. Migrate content:
+
+### **4️⃣ Migrate Content (Themes, Plugins)**  
 ```bash
-# In the wordpress service, copy new content to production
+# Copy new content to production
 cp -a wp-content-new/* wp-content/
 
-# Verify permissions on wp-content directory
+# Verify permissions on the wp-content directory
 chmod -R [appropriate-permissions] wp-content/
 ```
 
-5. Optional: Update database if needed:
+### **5️⃣ Optional: Database Updates for web address change**  
 ```bash
 ./update-db
+
+or
+
+docker compose exec wpcli_${COMPOSE_PROJECT_NAME} wp option update siteurl "https://mynewwebsite.com"
+docker compose exec wpcli_${COMPOSE_PROJECT_NAME} wp option update home "https://mynewwebsite.com"
+
 ```
 
-## Requirements
+---
-Docker
+## Tricks of the Trade
 
-## Contributing
+Cookie issues prevent login?  Add to beginning of wp-config.php.
-@bike
+```bash
+ob_start();
+```
 
-## License
+Change to a different template.  Perhaps the current one has broken the site?
-[GNU GENERAL PUBLIC LICENSE](LICENSE)
+```sql
+UPDATE wp_options SET option_value = 'twentytwentyfive' WHERE option_name = 'template';
+UPDATE wp_options SET option_value = 'twentytwentyfive' WHERE option_name = 'stylesheet';
+
+or
+
+docker compose exec wpcli_${COMPOSE_PROJECT_NAME} wp theme activate twentytwentyfive
+```
+
+Disable all plugins
+```sql
+UPDATE wp_options SET option_value = '' WHERE option_name = 'active_plugins';
+
+or
+
+docker compose exec wpcli_${COMPOSE_PROJECT_NAME} wp plugin deactivate --all
+```
+
+---
+
+## 📌 Requirements  
+- Docker
+
+---
+
+## 🤝 Contributing  
+For contributions, reach out to @bike .
+
+---
+
+## 📜 License  
+GNU GENERAL PUBLIC LICENSE

default.template.conf

@@ -5,7 +5,7 @@ server {
 
     listen       80;
     listen  [::]:80;
-    server_name wordpress;
+    server_name wordpress_${COMPOSE_PROJECT_NAME};
     root /var/www/html;
     index index.php;
 
@@ -24,11 +24,11 @@ server {
     }
 
 
-    # pass the PHP scripts to FastCGI server listening on wordpress2:9000
+    # pass the PHP scripts to FastCGI server listening on wordpress:9000
     #
     location ~ \.php$ {
         #fastcgi_split_path_info ^(.+\.php)(/.+)$;
-        fastcgi_pass   wordpress:9000;
+        fastcgi_pass   wordpress_${COMPOSE_PROJECT_NAME}:9000;
         fastcgi_index  index.php;
         fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
         include        fastcgi_params;

docker-compose.first.yml

@@ -7,6 +7,8 @@ services:
     build:
       context: .
       dockerfile: Dockerfile.wordpress_fpm
+      args:
+        WORDPRESS_VERSION: ${WORDPRESS_VERSION}    
     image: ${IMAGE_WEB:-web}       
     volumes:
       - html:/var/www/html          
@@ -24,8 +26,9 @@ services:
         max-file: "3"
     restart: always
     networks:
+      - custom_network
       - letsencrypt
-      - default
+
 
 volumes:
   html:
@@ -34,3 +37,5 @@ volumes:
 networks:
   letsencrypt:
     external: true
+  custom_network:
+    name: ${COMPOSE_PROJECT_NAME}_network  # Uses project-specific name     

docker-compose.template.yml

@@ -18,15 +18,17 @@
 
 services:
 
-  database:
+  database_${SERVICE_SUFFIX}:
     image: ${IMAGE_DATABASE:-database}
+    container_name: ${COMPOSE_PROJECT_NAME}_database
     volumes:
       - db:/var/lib/mysql
     environment:
+      - MYSQL_PASSWORD=${WORDPRESS_DB_PASSWORD:-fake}
+      - MYSQL_ROOT_PASSWORD=${WORDPRESS_DB_PASSWORD:-fake}
       - MYSQL_DATABASE=${MYSQL_DATABASE:-wordpress}
       - MYSQL_USER=${MYSQL_USER:-wordpress}
-      - MYSQL_PASSWORD=${MYSQL_PASSWORD:-fake}
+      - MARIADB_AUTO_UPGRADE=1             
-      - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD:-fake}   
     logging:
       driver: "json-file"  
       options:
@@ -34,20 +36,21 @@ services:
         max-file: "3"
     restart: always
     networks:
-      - letsencrypt
+      - custom_network
 
-  wordpress:
+  wordpress_${SERVICE_SUFFIX}:
-    # build:
-    #   context: .
-    #   dockerfile: Dockerfile.wordpress_fpm
     image: ${IMAGE_WEB:-wordpress}
+    container_name: ${COMPOSE_PROJECT_NAME}_wordpress    
     volumes:
       - html:/var/www/html
       - content:/var/www/html/wp-content
       - ./wp-config.php:/var/www/html/wp-config.php            
     environment:
-      - WORDPRESS_DB_HOST=${WORDPRESS_DB_HOST:-database:3306}      
+      - WORDPRESS_DB_HOST=database_${COMPOSE_PROJECT_NAME}:3306            
       - WORDPRESS_DB_PASSWORD=${WORDPRESS_DB_PASSWORD:-fake}
+      - MYSQL_DATABASE=${MYSQL_DATABASE:-wordpress}
+      - MYSQL_USER=${MYSQL_USER:-wordpress}
+      - TABLE_PREFIX=${TABLE_PREFIX:-wp_}             
       - VIRTUAL_HOST=${VIRTUAL_HOST:-wordpress}
       - LETSENCRYPT_HOST=${LETSENCRYPT_HOST:-wordpress}
       - LETSENCRYPT_EMAIL=${LETSENCRYPT_EMAIL:-me}
@@ -61,19 +64,21 @@ services:
     command: >
       bash -c "chown -R www-data:www-data /var/www/html/wp-content && php-fpm"   
     networks:
+      - custom_network
       - letsencrypt
-      - default
 
   # nginx:latest and/or can be customized      
-  web:
+  web_${SERVICE_SUFFIX}:
     # build:
     #   context: .
     #   dockerfile: Dockerfile.nginx
     image: nginx:latest
+    container_name: ${COMPOSE_PROJECT_NAME}_web 
     restart: always
     volumes:
       - html:/var/www/html/
       - content:/var/www/html/wp-content
+      - ./wp-config.php:/var/www/html/wp-config.php
       - ./default.conf:/etc/nginx/conf.d/default.conf
       - ./nginx.conf:/etc/nginx/nginx.conf
     environment:
@@ -82,8 +87,29 @@ services:
       - LETSENCRYPT_EMAIL=${LETSENCRYPT_EMAIL:-me}
       - LETSENCRYPT_TEST=${LETSENCRYPT_TEST:-true} 
     networks:
+      - custom_network
       - letsencrypt
-      - default   
+
+  wpcli_${SERVICE_SUFFIX}:
+    image: wordpress:cli
+    container_name: ${COMPOSE_PROJECT_NAME}_wpcli      
+    depends_on:
+      - database_${SERVICE_SUFFIX}
+      - wordpress_${SERVICE_SUFFIX}    
+    command: tail -f /dev/null  # Keeps the container running for CLI commands
+    volumes:
+      - html:/var/www/html
+      - content:/var/www/html/wp-content
+      - ./wp-config.php:/var/www/html/wp-config.php
+    user: "33:${HOST_GID}"  
+    environment:
+      - WORDPRESS_DB_HOST=database_${COMPOSE_PROJECT_NAME}:3306            
+      - WORDPRESS_DB_PASSWORD=${WORDPRESS_DB_PASSWORD:-fake}
+      - MYSQL_DATABASE=${MYSQL_DATABASE:-wordpress}
+      - MYSQL_USER=${MYSQL_USER:-wordpress}
+      - TABLE_PREFIX=${TABLE_PREFIX:-wp_}      
+    networks:
+      - custom_network
 
 # No variable substition for volumes in this version
 volumes:
@@ -99,5 +125,5 @@ volumes:
 networks:
   letsencrypt:
     external: true
-  # default:
+  custom_network:
-  #   name: ${COMPOSE_PROJECT_NAME}_default    
+    name: ${COMPOSE_PROJECT_NAME}_network  # Uses project-specific name      

generate-compose-nginx.sh

@@ -0,0 +1,41 @@
+#!/bin/bash
+
+# Docker service names are designed to be static, not dynamic, 
+# primarily due to the need for predictable and consistent communication 
+# between services within a Docker Compose environment.  However, since an
+# external letsencrypt network is utilized, conflicts occur if the service
+# name is not unique to the project.  This script resolves that issue by
+# generating a docker-compose.yml file with unique service names, which is
+# the COMPOSE_PROJECT_NAME
+
+# Load variables from .env file
+if [ -f .env ]; then
+    source .env
+fi
+
+export SERVICE_SUFFIX=${COMPOSE_PROJECT_NAME:-main}
+export COMPOSE_PROJECT_NAME
+export HOST_UID=$(id -u)
+export HOST_GID=$(id -g)
+envsubst < docker-compose.template.yml > docker-compose.yml
+
+if [ ! -f wp-config.conf ]; then
+    cp wp-config.template.php wp-config.php
+    chmod 0664 wp-config.php
+fi
+
+# Define the new value for the database host
+export new_wp="wordpress_${COMPOSE_PROJECT_NAME}"
+
+# If default.conf doesn't exist, create it from the template (using envsubst restricted to COMPOSE_PROJECT_NAME)
+if [ ! -f default.conf ]; then
+    echo "default.conf not found, creating from default.template.conf..."
+    envsubst '${COMPOSE_PROJECT_NAME}' < default.template.conf > default.conf
+fi
+
+# Check if the existing default.conf contains a database hostname matching the pattern (it may or may not contain the env variable placeholder)
+if grep -qE "\bwordpress_\w+(?::\d+)?\b" default.conf; then
+    # Update in-place only the portion that matches the database host pattern.
+    perl -pi -e 's/\bwordpress_\w+(?::(\d+))?\b/$ENV{"new_wp"} . (defined($1) ? ":$1" : "")/eg' default.conf
+    echo "default.conf updated with COMPOSE_PROJECT_NAME='${COMPOSE_PROJECT_NAME}'."
+fi

update-db

@@ -1,14 +1,19 @@
 #!/bin/bash
 
-source ".env"
+set -o allexport
+source .env
+set +o allexport
 
-website="https://$VIRTUAL_HOST"
+FIRST_VIRTUAL_HOST=$(echo "$VIRTUAL_HOST" | cut -d',' -f1)
-command="docker-compose exec database mysql"
+
+website="https://$FIRST_VIRTUAL_HOST"
+DATABASE_SERVICE="database_${COMPOSE_PROJECT_NAME}"
+command="docker compose exec $DATABASE_SERVICE mariadb"
 
 echo $website
 
-$command -u $MYSQL_USER $MYSQL_DATABASE -p"$WORDPRESS_DB_PASSWORD" -e "UPDATE cf_options SET option_value='$website' WHERE option_name='home';"
+$command -u $MYSQL_USER $MYSQL_DATABASE -p"$WORDPRESS_DB_PASSWORD" -e "UPDATE ${TABLE_PREFIX}options SET option_value='$website' WHERE option_name='home';"
-$command -u $MYSQL_USER $MYSQL_DATABASE -p"$WORDPRESS_DB_PASSWORD" -e "UPDATE cf_options SET option_value='$website' WHERE option_name='siteurl';"
+$command -u $MYSQL_USER $MYSQL_DATABASE -p"$WORDPRESS_DB_PASSWORD" -e "UPDATE ${TABLE_PREFIX}options SET option_value='$website' WHERE option_name='siteurl';"
 
 ## Add
 # /usr/bin/find /var/www/html/wp-content/uploads/ -type d -exec chmod 755 {} \; -o -type f -exec chmod 644 {} \; 

wp-config.template.php

@@ -20,13 +20,13 @@
 
 // ** MySQL settings - You can get this info from your web host ** //
 /** The name of the database for WordPress */
-define('DB_NAME', 'wordpress');
+define('DB_NAME', getenv('MYSQL_DATABASE'));
 
 /** MySQL database username */
-define('DB_USER', 'root');
+define('DB_USER', getenv('MYSQL_USER'));
 
 /** MySQL database password */
-define('DB_PASSWORD', 'wordpress');
+define('DB_PASSWORD', getenv('WORDPRESS_DB_PASSWORD'));
 
 /** MySQL hostname */
 define('DB_HOST', getenv('WORDPRESS_DB_HOST'));
@@ -63,7 +63,7 @@ define('NONCE_SALT',       '!M@7=}Gsx@4MVX|][e<N--f@BvkG_8,z5*8.G#lPr<Wrl0^0}hEV
  * You can have multiple installations in one database if you give each
  * a unique prefix. Only numbers, letters, and underscores please!
  */
-$table_prefix  = 'cf_';
+$table_prefix = getenv('TABLE_PREFIX') ?: 'wp_';
 
 /**
  * For developers: WordPress debugging mode.

wp-rocket-launch.sh

@@ -0,0 +1,51 @@
+#!/bin/bash
+
+# Define environment variables
+COMPOSE_FILE="docker-compose.first.yml"
+
+echo "🚀 Starting WordPress Deployment Process..."
+
+# Step 0: **Reset Environment** - Stop and remove volumes
+echo "🧹 Cleaning up existing containers and volumes..."
+docker compose down -v
+
+# Step 1: Build custom WordPress image
+echo "🔧 Building custom WordPress image..."
+docker compose -f "$COMPOSE_FILE" build
+
+# Step 2: Install or upgrade WordPress volume
+echo "📦 Installing or upgrading WordPress volume..."
+docker compose -f "$COMPOSE_FILE" up -d
+
+# Step 3: Stop WordPress container (keep HTML volume)
+echo "⏹️ Stopping WordPress container (keeping data)..."
+docker compose -f "$COMPOSE_FILE" down
+
+# Step 4: Start production environment
+echo "🚀 Launching production environment..."
+docker compose up -d
+
+# Step 5: Source .env and extract the first VIRTUAL_HOST address
+if [ -f .env ]; then
+    set -o allexport
+    source .env
+    set +o allexport
+
+    # Extract only the first address from VIRTUAL_HOST
+    FIRST_VIRTUAL_HOST=$(echo "$VIRTUAL_HOST" | cut -d',' -f1)
+
+    echo "✅ WordPress deployment complete! Site is live at: https://${FIRST_VIRTUAL_HOST}"
+else
+    echo "⚠️ .env file not found, VIRTUAL_HOST could not be displayed."
+fi
+
+# Step 6: Copy new WordPress content after deployment
+echo "📂 Copying new WordPress content to wp-content and correct permissions..."
+docker compose exec wordpress_${COMPOSE_PROJECT_NAME} bash -c "cp -a /var/www/html/wp-content-new/* /var/www/html/wp-content/"
+docker compose exec wordpress_${COMPOSE_PROJECT_NAME} bash -c "/usr/bin/find /var/www/html/wp-content -type d -exec chmod 755 {} \; -o -type f -exec chmod 644 {} \;"
+echo "✅ WordPress content successfully copied!"
+
+# Step 7: Shuffle salts
+echo "📂 Shuffle the salt keys...."
+docker compose exec wpcli_${COMPOSE_PROJECT_NAME} wp config shuffle-salts
+echo "✅ Wordpress salt keys sucessfully shuffled!"