update php 8.x images to bookworm (#141)

* update php 8.x images to bookworm

* ci bumps

* get images in first

* update docs links

* Don't forget imagick

Author: AaronFeledy

.github/workflows/build-php-images.yml

@@ -17,70 +17,70 @@ jobs:
       matrix:
         include:
           - image: php
-            tag: 8.4-fpm-4
+            tag: 8.4-fpm-5
             context: images/8.4-fpm
           - image: php
-            tag: 8.4-apache-4
+            tag: 8.4-apache-5
             context: images/8.4-apache
           - image: php
-            tag: 8.3-fpm-4
+            tag: 8.3-fpm-5
             context: images/8.3-fpm
           - image: php
-            tag: 8.3-apache-4
+            tag: 8.3-apache-5
             context: images/8.3-apache
           - image: php
-            tag: 8.2-fpm-4
+            tag: 8.2-fpm-5
             context: images/8.2-fpm
           - image: php
-            tag: 8.2-apache-4
+            tag: 8.2-apache-5
             context: images/8.2-apache
           - image: php
-            tag: 8.1-fpm-4
+            tag: 8.1-fpm-5
             context: images/8.1-fpm
           - image: php
-            tag: 8.1-apache-4
+            tag: 8.1-apache-5
             context: images/8.1-apache
           - image: php
-            tag: 8.0-fpm-4
+            tag: 8.0-fpm-5
             context: images/8.0-fpm
           - image: php
-            tag: 8.0-apache-4
+            tag: 8.0-apache-5
             context: images/8.0-apache
           - image: php
-            tag: 7.4-fpm-4
+            tag: 7.4-fpm-5
             context: images/7.4-fpm
           - image: php
-            tag: 7.4-apache-4
+            tag: 7.4-apache-5
             context: images/7.4-apache
           - image: php
-            tag: 7.3-fpm-4
+            tag: 7.3-fpm-5
             context: images/7.3-fpm
           - image: php
-            tag: 7.3-apache-4
+            tag: 7.3-apache-5
             context: images/7.3-apache
           - image: php
-            tag: 7.2-fpm-4
+            tag: 7.2-fpm-5
             context: images/7.2-fpm
           - image: php
-            tag: 7.2-apache-4
+            tag: 7.2-apache-5
             context: images/7.2-apache
           - image: php
-            tag: 7.1-fpm-4
+            tag: 7.1-fpm-5
             context: images/7.1-fpm
           - image: php
-            tag: 7.1-apache-4
+            tag: 7.1-apache-5
             context: images/7.1-apache
           - image: php
-            tag: 7.0-fpm-4
+            tag: 7.0-fpm-5
             context: images/7.0-fpm
           - image: php
-            tag: 7.0-apache-4
+            tag: 7.0-apache-5
             context: images/7.0-apache
           - image: php
-            tag: 5.6-fpm-4
+            tag: 5.6-fpm-5
             context: images/5.6-fpm
           - image: php
-            tag: 5.6-apache-4
+            tag: 5.6-apache-5
             context: images/5.6-apache
 
     steps:

.github/workflows/pr-docs-tests.yml

@@ -11,7 +11,7 @@ jobs:
         os:
           - ubuntu-24.04
         node-version:
-          - '18'
+          - '20'
     steps:
       # Install deps and cache
       - name: Checkout code

.github/workflows/pr-linter.yml

@@ -11,7 +11,7 @@ jobs:
         os:
           - ubuntu-24.04
         node-version:
-          - '18'
+          - '20'
     steps:
       # Install deps and cache
       - name: Checkout code

.github/workflows/pr-php-tests.yml

@@ -32,7 +32,7 @@ jobs:
         os:
           - ubuntu-24.04
         node-version:
-          - '18'
+          - '20'
     steps:
       - name: Checkout code
         uses: actions/checkout@v4

.github/workflows/pr-unit-tests.yml

@@ -13,7 +13,7 @@ jobs:
           - ubuntu-24.04
           - macos-12
         node-version:
-          - '18'
+          - '20'
     steps:
       # Install deps and cache
       - name: Checkout code

docs/caveats.md

@@ -25,4 +25,4 @@ Lando will set the `PATH` hierarchy for this service as follows:
 ]
 ```
 
-This is useful to note if you are not using absolute paths in any [tooling routes](https://docs.lando.dev/core/v3/tooling.html) and are getting the unexpected version of a particular utility.
+This is useful to note if you are not using absolute paths in any [tooling routes](https://docs.lando.dev/landofile/tooling.html) and are getting the unexpected version of a particular utility.

docs/config.md

@@ -5,9 +5,9 @@ description: Learn how to configure the Lando PHP service.
 
 # Configuration
 
-Here are the configuration options, set to the default values, for this service. If you are unsure about where this goes or what this means, we *highly recommend* scanning the [services documentation](https://docs.lando.dev/core/v3/services/lando.html) to get a good handle on how the magicks work.
+Here are the configuration options, set to the default values, for this service. If you are unsure about where this goes or what this means, we *highly recommend* scanning the [services documentation](https://docs.lando.dev/services/lando-3.html) to get a good handle on how the magicks work.
 
-Also note that options, in addition to the [build steps](https://docs.lando.dev/core/v3/services/lando.html#build-steps) and [overrides](https://docs.lando.dev/core/v3/services/lando.html#overrides) that are available to every service, are shown below:
+Also note that options, in addition to the [build steps](https://docs.lando.dev/services/lando-3.html#build-steps) and [overrides](https://docs.lando.dev/services/lando-3.html#overrides) that are available to every service, are shown below:
 
 ```yaml
 services:
@@ -193,9 +193,9 @@ composer_version: snapshot
 You can also use the `composer` key if you need to require any [global composer dependenices](https://getcomposer.org/doc/03-cli.md#require). This follows the same syntax as your normal [`composer.json`](https://getcomposer.org/doc/01-basic-usage.md#composer-json-project-setup) except written as YAML instead of JSON.
 
 ::: tip Use composer.json if you can
-While there are some legitimate use cases to globally install a composer dependency, it is almost always preferred to install using your applications normal `composer.json` and then running either `lando composer install` or alternatively setting up a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) that will automatically run before your app starts up.
+While there are some legitimate use cases to globally install a composer dependency, it is almost always preferred to install using your applications normal `composer.json` and then running either `lando composer install` or alternatively setting up a [build step](https://docs.lando.dev/services/lando-3.html#build-steps) that will automatically run before your app starts up.
 
-Note that `lando composer` is not provided out of the box by the `php` service and needs to be manually added by configuring your app's [tooling](https://docs.lando.dev/core/v3/tooling.html).
+Note that `lando composer` is not provided out of the box by the `php` service and needs to be manually added by configuring your app's [tooling](https://docs.lando.dev/landofile/tooling.html).
 :::
 
 An example of globally installing `phpunit/phpunit` `^6.5` is shown below:
@@ -208,7 +208,7 @@ services:
       phpunit/phpunit: ^6.5
 ```
 
-An example of using a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to automatically `composer install` your dependencies before your app starts is shown below:
+An example of using a [build step](https://docs.lando.dev/services/lando-3.html#build-steps) to automatically `composer install` your dependencies before your app starts is shown below:
 
 ```yaml
 services:
@@ -273,7 +273,7 @@ lando php
 lando composer
 ```
 
-Lando tooling is actually pretty powerful so definitely check out [the rest](https://docs.lando.dev/core/v3/tooling.html) of its cool features.
+Lando tooling is actually pretty powerful so definitely check out [the rest](https://docs.lando.dev/landofile/tooling.html) of its cool features.
 
 ## Adding routing
 
@@ -286,4 +286,4 @@ proxy:
     - something.else.local
 ```
 
-Lando proxying is actually pretty powerful so definitely check out [the rest](https://docs.lando.dev/core/v3/proxy.html) of its cool features.
+Lando proxying is actually pretty powerful so definitely check out [the rest](https://docs.lando.dev/landofile/proxy.html) of its cool features.

docs/extensions.md

@@ -75,11 +75,11 @@ Note that imagick is temporarily unavailable on PHP 8.3/8.4, due to a pending is
 
 There are a few ways you can extend or modify our php images below:
 
-* Using [build steps](https://docs.lando.dev/core/v3/services/lando.html#build-steps).
-* Using your own image with [service overrides](https://docs.lando.dev/core/v3/services/lando.html#overrides).
-* Building from your own local Dockerfile [service overrides](https://docs.lando.dev/core/v3/services/lando.html#using-dockerfiles).
+* Using [build steps](https://docs.lando.dev/services/lando-3.html#build-steps).
+* Using your own image with [service overrides](https://docs.lando.dev/services/lando-3.html#overrides).
+* Building from your own local Dockerfile [service overrides](https://docs.lando.dev/services/lando-3.html#using-dockerfiles).
 
-Consider the example that uses [build steps](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to install the `memcached` php extension as follows:
+Consider the example that uses [build steps](https://docs.lando.dev/services/lando-3.html#build-steps) to install the `memcached` php extension as follows:
 
 ```yaml
 services:

docs/guides/installing-extensions.md

@@ -27,7 +27,7 @@ Also note that you may need to adapt these slightly depending on the PHP version
 
 ## 1. Using build steps
 
-If installing your PHP extension is fairly trivial and not a long-running operation you may wish to simply use Lando [build-steps](https://docs.lando.dev/core/v3/services/lando.html#build-steps)
+If installing your PHP extension is fairly trivial and not a long-running operation you may wish to simply use Lando [build-steps](https://docs.lando.dev/services/lando-3.html#build-steps)
 
 Here is an example that uses build-steps to install the `xsl` and `stats` extensions.
 

docs/guides/installing-node.md

@@ -25,7 +25,7 @@ We've found installing `node` inside a Lando PHP service to generally be the pat
 
 ## 1. Using build steps
 
-Below is an example that installs `node12` using [build-steps](https://docs.lando.dev/core/v3/services/lando.html#build-steps).
+Below is an example that installs `node12` using [build-steps](https://docs.lando.dev/services/lando-3.html#build-steps).
 
 ```yaml
 services:
@@ -52,7 +52,7 @@ lando npm -v
 
 ## 2. Extending a Dockerfile
 
-If you are planning to extend your service with _additional_ build steps or would like to cache the build steps for a faster `lando rebuild` you should instead consider [extending with a Dockerfile](https://docs.lando.dev/core/v3/services/lando.html#using-dockerfiles) as in the example below:
+If you are planning to extend your service with _additional_ build steps or would like to cache the build steps for a faster `lando rebuild` you should instead consider [extending with a Dockerfile](https://docs.lando.dev/services/lando-3.html#using-dockerfiles) as in the example below:
 
 **.lando.yml**
 

docs/index.md

@@ -8,7 +8,7 @@ next: ./config.html
 
 [PHP](https://www.php.net/) is a popular scripting language that is especially suited for web development. It is often served by either [apache](https://docs.lando.dev/plugins/apache/) or [nginx](https://docs.lando.dev/plugins/nginx/).
 
-You can easily add it to your Lando app by adding an entry to the [services](https://docs.lando.dev/core/v3/services/lando.html) top-level config in your [Landofile](https://docs.lando.dev/core/v3).
+You can easily add it to your Lando app by adding an entry to the [services](https://docs.lando.dev/services/lando-3.html) top-level config in your [Landofile](https://docs.lando.dev).
 
 ```yaml
 services:
@@ -27,7 +27,7 @@ services:
 *   [8.0](https://hub.docker.com/r/devwithlando/php)
 *   **[7.4](https://hub.docker.com/r/devwithlando/php)** **(default)**
 *   [7.3](https://hub.docker.com/r/devwithlando/php)
-*   [custom](https://docs.lando.dev/core/v3/services/lando.html#overrides)
+*   [custom](https://docs.lando.dev/services/lando-3.html#overrides)
 
 ## Legacy versions
 
@@ -49,5 +49,5 @@ You can still run these versions with Lando but for all intents and purposes the
 
 Because we use our own custom images for `php`, specifying a patch version is not currently supported.
 
-If you **really** need to lock down to a patch version, you could consider using either a [custom compose service](https://docs.lando.dev/plugins/compose) or a service [overrides](https://docs.lando.dev/core/v3/services/lando.html#overrides).
+If you **really** need to lock down to a patch version, you could consider using either a [custom compose service](https://docs.lando.dev/plugins/compose) or a service [overrides](https://docs.lando.dev/services/lando-3.html#overrides).
 

images/5.6-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:5.6-apache-4 .
+# docker build -t devwithlando/php:5.6-apache-5 .
 
 FROM php:5.6-apache-stretch
 

images/5.6-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:5.6-fpm-4 .
+# docker build -t devwithlando/php:5.6-fpm-5 .
 
 FROM php:5.6-fpm-stretch
 

images/7.0-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.0-apache-4 .
+# docker build -t devwithlando/php:7.0-apache-5 .
 
 FROM php:7.0-apache-stretch
 

images/7.0-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.0-fpm-4 .
+# docker build -t devwithlando/php:7.0-fpm-5 .
 
 FROM php:7.0-fpm-stretch
 

images/7.1-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.1-apache-4 .
+# docker build -t devwithlando/php:7.1-apache-5 .
 
 FROM php:7.1-apache-buster
 

images/7.1-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.1-fpm-4 .
+# docker build -t devwithlando/php:7.1-fpm-5 .
 
 FROM php:7.1-fpm-buster
 

images/7.2-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.2-apache-4 .
+# docker build -t devwithlando/php:7.2-apache-5 .
 
 FROM php:7.2-apache-buster
 

images/7.2-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.2-fpm-4 .
+# docker build -t devwithlando/php:7.2-fpm-5 .
 
 FROM php:7.2-fpm-buster
 

images/7.3-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.3-apache-4 .
+# docker build -t devwithlando/php:7.3-apache-5 .
 
 FROM php:7.3-apache-bullseye
 

images/7.3-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.3-fpm-4 .
+# docker build -t devwithlando/php:7.3-fpm-5 .
 
 FROM php:7.3-fpm-bullseye
 

images/7.4-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.4-apache-4 .
+# docker build -t devwithlando/php:7.4-apache-5 .
 
 FROM php:7.4-apache-bullseye
 

images/7.4-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:7.4-fpm-4 .
+# docker build -t devwithlando/php:7.4-fpm-5 .
 
 FROM php:7.4-fpm-bullseye
 

images/8.0-apache/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:8.0-apache-4 .
+# docker build -t devwithlando/php:8.0-apache-5 .
 
 FROM php:8.0-apache-bullseye
 

images/8.0-fpm/Dockerfile

@@ -1,4 +1,4 @@
-# docker build -t devwithlando/php:8.0-fpm-4 .
+# docker build -t devwithlando/php:8.0-fpm-5 .
 
 FROM php:8.0-fpm-bullseye