From 27fc5aaf7b83f85dc9de4fa08615748a8964abe0 Mon Sep 17 00:00:00 2001 From: Jonathan Visser Date: Wed, 14 May 2025 10:43:49 +0200 Subject: [PATCH] Add and use Hypernode Deploy PHP 8.4 image --- .github/workflows/cleanup_acceptance.yaml | 2 +- .github/workflows/deploy.yaml | 6 +++--- .../getting-started/configure-ci-cd.md | 8 ++++---- docs/hypernode-deploy/pipelines/bitbucket-pipelines.md | 8 ++++---- docs/hypernode-deploy/pipelines/github-actions.md | 10 +++++----- docs/hypernode-deploy/pipelines/gitlab-ci.md | 6 +++--- ...eploy-your-application-using-hypernode-deploy-v1.md | 6 +++--- .../how-to-use-the-hypernode-systemctl-cli-tool.md | 2 +- 8 files changed, 24 insertions(+), 24 deletions(-) diff --git a/.github/workflows/cleanup_acceptance.yaml b/.github/workflows/cleanup_acceptance.yaml index 35d24c80..f4708852 100644 --- a/.github/workflows/cleanup_acceptance.yaml +++ b/.github/workflows/cleanup_acceptance.yaml @@ -7,7 +7,7 @@ on: jobs: cleanup: runs-on: ubuntu-latest - container: quay.io/hypernode/deploy:latest-php8.3-node20 + container: quay.io/hypernode/deploy:latest-php8.4-node22 environment: acceptance steps: - uses: actions/checkout@v2 diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml index 621666f4..ec3fe3ea 100644 --- a/.github/workflows/deploy.yaml +++ b/.github/workflows/deploy.yaml @@ -12,7 +12,7 @@ env: jobs: build: runs-on: ubuntu-latest - container: quay.io/hypernode/deploy:latest-php8.3-node20 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v3 with: @@ -47,7 +47,7 @@ jobs: name: acceptance url: ${{ steps.get_brancher_hostname.outputs.BRANCHER_URL }} if: github.ref != 'refs/heads/master' - container: quay.io/hypernode/deploy:latest-php8.3-node20 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v3 with: @@ -102,7 +102,7 @@ jobs: name: production url: https://docs.hypernode.io if: github.ref == 'refs/heads/master' - container: quay.io/hypernode/deploy:latest-php8.3-node20 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v3 - name: download build artifact diff --git a/docs/hypernode-deploy/getting-started/configure-ci-cd.md b/docs/hypernode-deploy/getting-started/configure-ci-cd.md index e5dc76bf..e85c5999 100644 --- a/docs/hypernode-deploy/getting-started/configure-ci-cd.md +++ b/docs/hypernode-deploy/getting-started/configure-ci-cd.md @@ -103,8 +103,8 @@ env: jobs: build: runs-on: ubuntu-latest - # Here we use the latest Hypernode Deploy image with PHP 8.3 and Node.js 22 - container: quay.io/hypernode/deploy:latest-php8.3-node22 + # Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v2 - uses: actions/cache@v2 @@ -137,8 +137,8 @@ jobs: deploy: needs: build runs-on: ubuntu-latest - # Here we use the latest Hypernode Deploy image with PHP 8.3 and Node.js 22 - container: quay.io/hypernode/deploy:latest-php8.3-node22 + # Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v2 - name: download build artifact diff --git a/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md b/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md index 3f650781..9ea2bed3 100644 --- a/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md +++ b/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md @@ -58,8 +58,8 @@ Create the file `bitbucket-pipelines.yml` with the contents below. This workflow will be used in other workflows. ```yaml -# Here we use the latest Hypernode Deploy image with PHP 8.3 and Node.js 22 -image: quay.io/hypernode/deploy:latest-php8.3-node22 +# Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22 +image: quay.io/hypernode/deploy:latest-php8.4-node22 definition: steps: @@ -73,9 +73,9 @@ definition: ````{note} Don't forget to set the specifications of the image to what your project needs. The same goes for the deploy steps. -For example, if your project needs PHP 8.3 and Node.js 22, set the image to: +For example, if your project needs PHP 8.4 and Node.js 22, set the image to: ```yaml -image: quay.io/hypernode/deploy:latest-php8.3-node22 +image: quay.io/hypernode/deploy:latest-php8.4-node22 ``` ```` diff --git a/docs/hypernode-deploy/pipelines/github-actions.md b/docs/hypernode-deploy/pipelines/github-actions.md index 6a2c53dc..f084ebb2 100644 --- a/docs/hypernode-deploy/pipelines/github-actions.md +++ b/docs/hypernode-deploy/pipelines/github-actions.md @@ -58,7 +58,7 @@ jobs: build: runs-on: ubuntu-latest # See https://quay.io/repository/hypernode/deploy?tab=tags for all possible tags. - container: quay.io/hypernode/deploy:latest-php8.3-node22 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v3 - uses: actions/cache@v3 @@ -79,11 +79,11 @@ jobs: ````{note} Don't forget to set the specifications of the image to what your project needs. The same goes for the deploy steps. -For example, if your project needs PHP 8.3 and Node.js 22, set the image to: +For example, if your project needs PHP 8.4 and Node.js 22, set the image to: ```yaml jobs: build: - container: quay.io/hypernode/deploy:latest-php8.3-node22 + container: quay.io/hypernode/deploy:latest-php8.4-node22 ... ``` ```` @@ -113,7 +113,7 @@ jobs: environment: name: production url: https://www.example.com - container: quay.io/hypernode/deploy:latest-php8.3-node22 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v3 - name: download build artifact @@ -157,7 +157,7 @@ jobs: environment: name: acceptance url: https://acceptance.example.com - container: quay.io/hypernode/deploy:latest-php8.3-node22 + container: quay.io/hypernode/deploy:latest-php8.4-node22 steps: - uses: actions/checkout@v3 - name: download build artifact diff --git a/docs/hypernode-deploy/pipelines/gitlab-ci.md b/docs/hypernode-deploy/pipelines/gitlab-ci.md index c5a7e75c..c804a40c 100644 --- a/docs/hypernode-deploy/pipelines/gitlab-ci.md +++ b/docs/hypernode-deploy/pipelines/gitlab-ci.md @@ -49,7 +49,7 @@ This sets the container image, defines the CI/CD stages and defines the build st ```yaml # See https://quay.io/repository/hypernode/deploy?tab=tags for all possible tags. -image: quay.io/hypernode/deploy:latest-php8.3-node22 +image: quay.io/hypernode/deploy:latest-php8.4-node22 stages: - build @@ -70,9 +70,9 @@ build: ````{note} Don't forget to set the specifications of the image to what your project needs. -For example, if your project needs PHP 8.3 and Node.js 16, set the image to: +For example, if your project needs PHP 8.4 and Node.js 16, set the image to: ```yaml -image: quay.io/hypernode/deploy:latest-php8.3-node16 +image: quay.io/hypernode/deploy:latest-php8.4-node16 ``` ```` diff --git a/docs/hypernode-platform/tools/how-to-deploy-your-application-using-hypernode-deploy-v1.md b/docs/hypernode-platform/tools/how-to-deploy-your-application-using-hypernode-deploy-v1.md index f8b8c3a0..490f5525 100644 --- a/docs/hypernode-platform/tools/how-to-deploy-your-application-using-hypernode-deploy-v1.md +++ b/docs/hypernode-platform/tools/how-to-deploy-your-application-using-hypernode-deploy-v1.md @@ -142,7 +142,7 @@ Now it's time to create your CI configuration file. You can either start from sc The CI configuration file needs to make use of the Hypernode Deploy image in order to run your CI/CD pipelines succesfully. We serve multiple flavors of the Hypernode Deploy image, one for every PHP + NodeJS version combination. See [our image repository](https://quay.io/repository/hypernode/deploy?tab=tags&tag=latest) for all supported flavors. As new PHP / Node versions come out, we'll bake more images to support those. -Choose a version of the hypernode/deploy image that best reflects your application needs. Here's an example of a `.github/workflows/deploy.yml` file that uses the PHP 8.3 + Node 20 flavor and is configured with a configuration for the staging environment, containing a build step and deploy step to perform the deployment to the configured staging server. It uses the configuration provided in `deploy.php` to perform the steps. +Choose a version of the hypernode/deploy image that best reflects your application needs. Here's an example of a `.github/workflows/deploy.yml` file that uses the PHP 8.4 + Node 22 image and is configured with a configuration for the staging environment, containing a build step and deploy step to perform the deployment to the configured staging server. It uses the configuration provided in `deploy.php` to perform the steps. ```yaml # This file would need to be placed in .github/workflows/deploy.yaml for example @@ -166,7 +166,7 @@ defaults: jobs: build: runs-on: ubuntu-latest - container: quay.io/hypernode/deploy:latest-php8.3-node20 + container: quay.io/hypernode/deploy:latest-php8.4-node20 steps: - uses: actions/checkout@v2 - uses: actions/cache@v2 @@ -186,7 +186,7 @@ jobs: deploy_staging: needs: build runs-on: ubuntu-latest - container: quay.io/hypernode/deploy:latest-php8.3-node20 + container: quay.io/hypernode/deploy:latest-php8.4-node20 steps: - uses: actions/checkout@v2 - name: download build artifact diff --git a/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md b/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md index e479779c..ab9f43f2 100644 --- a/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md +++ b/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md @@ -86,7 +86,7 @@ To see which value a setting has you can run the following: To set a setting to a certain value you can run the following: -`hypernode-systemctl settings php_version 8.3` +`hypernode-systemctl settings php_version 8.4` If an invalid value is provided you will be notified of this during the setting procedure.