dockerpress-base-image

A great base image for WordPress sites.

Usage

The base image is available on both Docker Hub and GitHub Container Registry.

We provide multiple tags for images, below are some common examples:

# To use a specific semantic version
FROM evermadefi/dockerpress-base-image:2.1.10

# To use a specific semantic minor version
FROM evermadefi/dockerpress-base-image:2.1

# To use a specific semantic major version
FROM evermadefi/dockerpress-base-image:2

# To use a specific tag
FROM evermadefi/dockerpress-base-image:v2.1.10

# To use a specific branch
FROM evermadefi/dockerpress-base-image:master

# To use a specific commit hash
FROM evermadefi/dockerpress-base-image:c2f03ceda98b8df754d27c7b246eea7181351880

# To use GitHub Container Registry instead of Docker Hub (you can use all the same tags described above)
FROM ghcr.io/evermade/dockerpress-base-image:2.1.10

To simply just pull the image or update a stale local copy, run the docker pull command like so with the tag you wish you pull:

docker pull evermadefi/dockerpress-base-image:2.1.10

And for GitHub Container Registry, same thing:

docker pull ghcr.io/evermade/dockerpress-base-image:2.1.10

And enjoy!

Contributing

1. Commit any necessary changes to the Dockerfile on your branch

2. Create a pull request to the appropriate branch (such as master) from your branch

3. Make sure your pull request passes the automatic build workflow and fix appropriately if needed

4. Request a pull request review

5. Have the pull request approved and merged to master

6. Once merged to master, a new build process will be automatically dispatched and once complete, the new image will be pushed to container registries with both the long and short commit hash and branch name as tags. The build process also automatically applies Open Containers labels to the images.

Publishing a new version

1. Draft a new release on GitHub using the MAJOR.MINOR.PATCH semantic versioning scheme for the new tag with the "v" prefix (e.g. v2.1.11). You can also create and push a tag separately using your preferred Git client, but GitHub allows you to do this all at once, so it is not necessary.

2. Write a description with the changelog for the release using the following template:

   # Changelog summary
   
   - Updated PHP base image to [8.1.28](https://www.php.net/ChangeLog-8.php#8.1.28)
   
   https://hub.docker.com/r/evermadefi/dockerpress-base-image/
   https://github.com/evermade/dockerpress-base-image/pkgs/container/dockerpress-base-image

3. Publish the new release

4. This automatically triggers the image builder GitHub Workflow and will, eventually, after some 30 minutes, push the new images with the appropriate tags and labels to Docker Hub and GitHub Container Registry. So, go get a cup of ☕️ while you wait.

5. Once the build workflow is complete, you can pull the new image from either of the container registries as shown in the Usage section.

Adding third party downloads

1. Check the integrity of the source yourself, that the contents are correct.

2. Install an ADD instruction with the checksum and appropriate owner and permissions.

3. If available, verify the file signatures with a known good GPG key.

If the build is throwing a checksum mismatch error, the file contents must have changed and must be re-verified.

If the signature cannot be verified, the file is not signed by a known good GPG key. If the GPG key used to sign the file looks valid, you should add it to the GPG key list.

Updating certbot and its dependencies

1. Additional dependencies may be added to the certbot-requirements.in file if required.

2. pip-compile --allow-unsafe --generate-hashes certbot-requirements.in

3. Verify that the requirements are legit.