Update documentation and Dockerfiles to support PHP 8.5, including changes to image references across various guides and examples. Adjusted configurations in multiple files to reflect the new version.

Author: jaydrogers

docs/content/docs/1.getting-started/2.container-basics.md

@@ -18,8 +18,8 @@ There are some important terms to understand when working with containers:
 | Term | Definition |
 |------|------------|
 | Container | A running instance of an image. |
-| Image | A template for a container to start with (ie. `serversideup/php:8.4-frankenphp`). |
-| Tag | A specific version of an image (ie. `8.4-frankenphp`). |
+| Image | A template for a container to start with (ie. `serversideup/php:8.5-frankenphp`). |
+| Tag | A specific version of an image (ie. `8.5-frankenphp`). |
 | Registry | A repository of images. This is where users can pull images from to start a container. This can be places like [Docker Hub](https://hub.docker.com/r/serversideup/php) or [GitHub Packages](https://github.com/serversideup/docker-php/pkgs/container/php). |
 | Volume | A directory on your host machine that is mounted into a container. This allows you to share files between your host machine and the container. |
 | Port | Ports are virtual numbers organizing network data traffic, directing it to the correct application on a device. If you want to expose traffic to work with `http://localhost`, you would map port `80` on your host machine to port `8080` on the container. |
@@ -57,9 +57,9 @@ So although we're going to show you best practices with Docker, this means you'l
 If you followed our [installation guide](/docs/getting-started/installation), you've already run containers and seen them in action. Let's break down what actually happened when you ran `docker compose up`.
 
 ### Images vs Containers
-Think of an **image** as a blueprint and a **container** as the actual running instance of that blueprint. When you specified `image: serversideup/php:8.4-fpm-nginx` in your `compose.yml`, you told Docker to:
+Think of an **image** as a blueprint and a **container** as the actual running instance of that blueprint. When you specified `image: serversideup/php:8.5-fpm-nginx` in your `compose.yml`, you told Docker to:
 
-1. Download the `serversideup/php:8.4-fpm-nginx` image (the blueprint)
+1. Download the `serversideup/php:8.5-fpm-nginx` image (the blueprint)
 2. Create a container from that image (the running instance)
 3. Start the container with your specified configuration
 
@@ -84,7 +84,7 @@ In your `compose.yml`, when you define a service called `php`, you're telling Do
 ```yml [compose.yml] {2}
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - 80:8080
 ```

docs/content/docs/2.image-variations/fpm-apache.md

@@ -79,7 +79,7 @@ Here are a few examples to help you get started with the FPM-Apache variation.
 
 ### Docker CLI
 ```bash [Terminal]
-docker run -p 80:8080 -v $(pwd):/var/www/html/public serversideup/php:8.4-fpm-apache
+docker run -p 80:8080 -v $(pwd):/var/www/html/public serversideup/php:8.5-fpm-apache
 ```
 
 Your application will be available at `http://localhost`. The default document root is `/var/www/html/public`.
@@ -94,7 +94,7 @@ This is the recommended approach for local development and production deployment
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-apache
+    image: serversideup/php:8.5-fpm-apache
     ports:
       - "80:8080"
       - "443:8443"
@@ -115,7 +115,7 @@ The FPM-Apache variation is excellent for WordPress hosting:
 ```yml [compose.yml]
 services:
   wordpress:
-    image: serversideup/php:8.4-fpm-apache
+    image: serversideup/php:8.5-fpm-apache
     ports:
       - "80:8080"
       - "443:8443"
@@ -163,7 +163,7 @@ The FPM-Apache variation includes built-in SSL support with self-signed certific
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-apache
+    image: serversideup/php:8.5-fpm-apache
     ports:
       - "8080:8080"
       - "8443:8443"
@@ -184,7 +184,7 @@ For production, use your own SSL certificates:
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-apache
+    image: serversideup/php:8.5-fpm-apache
     ports:
       - "443:8443"
     volumes:

docs/content/docs/2.image-variations/fpm-nginx.md

@@ -75,7 +75,7 @@ Here are a few examples to help you get started with the FPM-NGINX variation.
 
 ### Docker CLI
 ```bash [Terminal]
-docker run -p 80:8080 -v $(pwd):/var/www/html/public serversideup/php:8.4-fpm-nginx
+docker run -p 80:8080 -v $(pwd):/var/www/html/public serversideup/php:8.5-fpm-nginx
 ```
 
 Your application will be available at `http://localhost`. The default webroot is `/var/www/html/public`.
@@ -91,7 +91,7 @@ This is the recommended approach for local development and production deployment
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - "80:8080"
     volumes:
@@ -110,7 +110,7 @@ The FPM-NGINX variation is perfectly suited for Laravel applications:
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - "80:8080"
       - "443:8443"
@@ -163,7 +163,7 @@ The FPM-NGINX variation includes built-in SSL support with self-signed certifica
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - "80:8080"
       - "443:8443"
@@ -184,7 +184,7 @@ For production, use your own SSL certificates:
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - "443:8443"
     volumes:
@@ -249,7 +249,7 @@ If you're running an application in production, you'll likely want to package yo
 services:
   php:
     # You'll likely replace this with your own custom image name
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     environment:
       # Enable OPcache for production
       PHP_OPCACHE_ENABLE: "1"
@@ -264,7 +264,7 @@ services:
 services:
   php:
     # You'll likely replace this with your own custom image name
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     environment:
       # NGINX Settings
       NGINX_CLIENT_MAX_BODY_SIZE: "200M"
@@ -300,7 +300,7 @@ You can add custom NGINX server configuration by mounting files:
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - "80:8080"
     volumes:

docs/content/docs/2.image-variations/fpm.md

@@ -67,7 +67,7 @@ This example shows a common setup with PHP-FPM in one container and NGINX in ano
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm
+    image: serversideup/php:8.5-fpm
     volumes:
       - ./:/var/www/html
 
@@ -119,7 +119,7 @@ The `php-fpm-healthcheck` script can also monitor specific metrics like accepted
 ```yml [compose.yml]{7-10}
 services:
   php:
-    image: serversideup/php:8.4-fpm
+    image: serversideup/php:8.5-fpm
     volumes:
       - ./:/var/www/html
     healthcheck:
@@ -154,7 +154,7 @@ The FPM variation gives you fine-grained control over PHP process management. He
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm
+    image: serversideup/php:8.5-fpm
     environment:
       PHP_FPM_PM_CONTROL: "static"
       PHP_FPM_PM_MAX_CHILDREN: "50"
@@ -165,7 +165,7 @@ services:
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm
+    image: serversideup/php:8.5-fpm
     environment:
       PHP_FPM_PM_CONTROL: "ondemand"
       PHP_FPM_PM_MAX_CHILDREN: "10"

docs/content/docs/2.image-variations/frankenphp.md

@@ -85,7 +85,7 @@ Health checks are critical for zero-downtime deployments, but the official image
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     environment:
       # Use Laravel's built-in health check
       HEALTHCHECK_PATH: /up
@@ -222,7 +222,7 @@ Here are a few examples to help you get started with the FrankenPHP variation.
 ### Docker CLI
 
 ```bash [Terminal]
-docker run -p 80:8080 -v $(pwd):/var/www/html/public serversideup/php:8.4-frankenphp
+docker run -p 80:8080 -v $(pwd):/var/www/html/public serversideup/php:8.5-frankenphp
 ```
 
 Your application will be available at `http://localhost`. The default webroot is `/var/www/html/public`.
@@ -240,7 +240,7 @@ Don't forget to create a `public` directory and put your PHP code in there.
 services:
   php:
     # Choose our PHP version and variation
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     # Expose and map HTTP and HTTPS ports
     ports:
       - 80:8080
@@ -292,7 +292,7 @@ See our [Configuring SSL](/docs/deployment-and-production/configuring-ssl) guide
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     ports:
       - "80:8080"
       - "443:8443"
@@ -315,7 +315,7 @@ For local development, use the `SSL_MODE` environment variable:
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     ports:
       - "80:8080"
       - "443:8443"
@@ -389,7 +389,7 @@ There are a few areas where you can use environment variables to customize your
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     environment:
       CADDY_SERVER_EXTRA_DIRECTIVES: |
         # Add custom headers

docs/content/docs/3.framework-guides/1.laravel/octane.md

@@ -36,7 +36,7 @@ By default, FrankenPHP runs in classic mode. Your compose file might look someth
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     ports:
       - "80:8080"
     volumes:
@@ -78,7 +78,7 @@ Laravel Octane provides its own Caddyfile. This may cause some of the serverside
 ```yml [compose.yml]{8-13}
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     ports:
       - "80:8080"
     volumes:

docs/content/docs/3.framework-guides/2.wordpress/4.using-wordpress-with-docker.md

@@ -91,7 +91,7 @@ Here's a proven WordPress stack running on Docker Swarm that balances containeri
 
 **Infrastructure components:**
 1. [Traefik](https://traefik.io/traefik/){target="_blank"} - Automatic SSL with Let's Encrypt and request routing
-2. [serversideup/php:8.4-fpm-apache](https://hub.docker.com/r/serversideup/php/tags?name=fpm-apache){target="_blank"} - PHP with Apache for WordPress compatibility
+2. [serversideup/php:8.5-fpm-apache](https://hub.docker.com/r/serversideup/php/tags?name=fpm-apache){target="_blank"} - PHP with Apache for WordPress compatibility
 3. [MariaDB](https://hub.docker.com/_/mariadb){target="_blank"} - MySQL-compatible database without Oracle licensing
 
 ::tip
@@ -136,7 +136,7 @@ Treating containers as the runtime environment while keeping WordPress files on
 ```yml [compose.yml]
 services:
   wordpress:
-    image: serversideup/php:8.4-fpm-apache
+    image: serversideup/php:8.5-fpm-apache
     volumes:
       - ./:/var/www/html
     ports:

docs/content/docs/4.deployment-and-production/3.packaging-your-app-for-deployment.md

@@ -17,7 +17,7 @@ In the [installation guide](/docs/getting-started/installation), your `compose.y
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - 80:8080
     volumes:
@@ -33,7 +33,7 @@ This works great for development because:
 For production, you'll create a **custom image** that includes your application code:
 
 ```dockerfile [Dockerfile]
-FROM serversideup/php:8.4-fpm-nginx
+FROM serversideup/php:8.5-fpm-nginx
 
 # Copy your application code into the image
 COPY --chown=www-data:www-data . /var/www/html
@@ -56,7 +56,7 @@ The `Dockerfile` should live at the root of your project, in the same directory
 For a simple PHP application, your Dockerfile might look like this:
 
 ```dockerfile [Dockerfile]
-FROM serversideup/php:8.4-fpm-nginx
+FROM serversideup/php:8.5-fpm-nginx
 
 # Switch to root to install dependencies and copy files
 USER root
@@ -116,7 +116,7 @@ Don't use `latest` tags in production. Use specific versions:
 FROM serversideup/php:latest
 
 # Good - explicitly versioned
-FROM serversideup/php:8.4-fpm-nginx
+FROM serversideup/php:8.5-fpm-nginx
 ```
 
 ### 2. Run as non-root user

docs/content/docs/4.deployment-and-production/4.configuring-ssl.md

@@ -115,7 +115,7 @@ Here's an example of directly exposing FrankenPHP to the internet with automatic
 ```yml [compose.yml]
 services:
   php:
-    image: serversideup/php:8.4-frankenphp
+    image: serversideup/php:8.5-frankenphp
     ports:
       - 80:8080
       - 443:8443
@@ -164,7 +164,7 @@ Set your private key file permissions to `600` (read/write for owner only). Inco
 ```yml [compose.yml]{8-10,13}
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - 80:8080
       - 443:8443
@@ -228,7 +228,7 @@ While browsers will show warnings, self-signed certificates are useful for speci
 ```yml [compose.yml]{7-9}
 services:
   php:
-    image: serversideup/php:8.4-fpm-nginx
+    image: serversideup/php:8.5-fpm-nginx
     ports:
       - 80:8080
       - 443:8443

docs/content/docs/5.guide/1.migrating-from-official-php-images.md

@@ -45,17 +45,17 @@ Review our [choosing an image](/docs/getting-started/choosing-an-image) guide to
 
 #### Update your `Dockerfile` or `compose.yml` file
 :::tip
-We simply change `php:8.4-apache` to `serversideup/php:8.4-fpm-apache`
+We simply change `php:8.5-apache` to `serversideup/php:8.5-fpm-apache`
 :::
 **Dockerfile**
 :::code-group
 ```dockerfile [ORIGINAL: Dockerfile]{1}
-FROM php:8.4-apache
+FROM php:8.5-apache
 
 # Rest of your Dockerfile...
 ```
 ```dockerfile [UPDATED: Dockerfile]{1}
-FROM serversideup/php:8.4-fpm-apache
+FROM serversideup/php:8.5-fpm-apache
 
 # Rest of your Dockerfile...
 ```
@@ -66,15 +66,15 @@ FROM serversideup/php:8.4-fpm-apache
 ```yml [ORIGINAL: compose.yml]{3,5-6}
 services:
   php:
-    image: php:8.4-apache
+    image: php:8.5-apache
     ports:
       - 80:80
       - 443:443
 ```
 ```yml [UPDATED: compose.yml]{3,5-6}
 services:
   php:
-    image: serversideup/php:8.4-fpm-apache
+    image: serversideup/php:8.5-fpm-apache
     ports:
       - 80:8080
       - 443:8443