Thanks for your interest in contributing to this project! Please use read this entire guide before submitting a pull request.

Project dependencies

You must have these installed on your system.

How things work

  1. All files are stored in the /src folder
  2. Github Actions will automatically build and deploy the images

Running things locally

To run a build, simply run ./scripts/ (with Docker Desktop running). This will show you a help menu with all the available options.

Example: Building a Unit image running PHP 8.2.12 on Debian Bookworm

bash scripts/ --variation unit --version 8.2.12 --os bookworm

This will build serversideup/php:8.2.12-unit-bookworm locally on your machine for testing and inspection.

Published Beta Images

We also have beta images that are published from the release/v3.0 branch (or the "main" branch once v3.0 is released).

Debian Variations

⚙️ Variation🚀 Version

Alpine Variations

To see the size difference between Debian and Alpine, here is a list of our Alpine versions:

⚙️ Variation🚀 Version
unit⚠️ Unit does not have an Alpine version. See the known issue →

Running a test web server:

Sometimes you need to just run a test web server locally to see if your changes work. Below is a good example on how to quickly do this.

Example: Run a simple container for testing

docker run --rm -v $(pwd):/var/www/html -p 80:80 -p 443:443 serversideup/php:beta-8.3-fpm-nginx

How PHP Versions are selected for distribution

We use the official PHP versions as our base image. To identify which versions should be built, we use a file called scripts/conf/php-versions-base-config.yml to explicitly select what versions should be built and any special rules/settings for each version (like base OS, default versions, etc).

We then use a scripts/ script to download the latest active releases from PHP and merge them into a final file called scripts/conf/php-versions.yml.

The php-versions.yml file will include all final versions for tagging and building.

We generate our tags with a file called scripts/ which handles all the advanced logic of compiling our tags together.

All the scripts above are designed to run locally and in GitHub Actions. Feel free to execute these scripts to see the help menus and how they work.

GitHub Actions

We use GitHub Actions exclusively to publish all of our releases. If the image exists from DockerHub or GitHub Packages, it will never be published from a local machine.

See .github/workflows/action_publish-beta-images.yml for an example of how we publish our beta images.

Helping out

If you're really eager to help out, here are a few places to get started: