t3kit / t3kit-dockerhub

t3kit Docker images placed on Docker Hub

t3kit-dockerhub

Docker images to run t3kit and TYPO3 locally

Table of contents

• About
• Required dependencies
• Image naming convention
• File structure
• t3kit Docker images

General info about t3kit project

• Documentation
• t3kit Roadmap
• Versioning
• t3kit project structure
• Contributing to t3kit
• Code of Conduct
• Support
• Security Policy

---

About

t3kit-dockerhub is a bunch of Docker images to use with t3kit project and TYPO3 for local development and testing

Required dependencies

• Docker >= v20.10.8
• Docker Compose >= v2.0.0

Image naming convention

Example: t3kit/10-php7.4-fpm-nginx-buster:1.0.0

t3kit version	PHP version	HTTP Server	base OS	Image version (semver)
t3kit/10	php7.4-fpm	nginx	debian buster	:1.0.0

File structure

t3kit-dockerhub/
├── .github/             # github actions
├── nproxy/
│   ├── Dockerfile
│   └── nginx.tmpl       # nginx template
├── mkcert/
│   ├── Dockerfile
│   └── docker-entrypoint.sh
├── t3kit8.9/
│   └── php7.4-apache2.4-ubuntu18.04/
│       ├── Dockerfile
│       ├── typo3.conf     # TYPO3 apache virtual host config
│       └── typo3.ini      # TYPO3 php config
└── t3kit10/
    └── php7.4-fpm-nginx-buster/
        ├── docker-entrypoint.sh
        ├── Dockerfile
        ├── typo3.ini                # TYPO3 php config
        └── configuration/nginx.conf # nginx config

t3kit Docker images

t3kit/10-php7.4-fpm-nginx-buster

Docker image with nginx server and PHP-FPM preinstalled

os="debian:buster-slim"
php="7.4"
nginx="1.18.0"
support.t3kit="10"
support.typo3="10"
image.name="t3kit/10-php7.4-fpm-nginx-buster"

t3kit/11-php8-fpm-nginx-buster

Docker image with nginx server and PHP-FPM preinstalled

os="debian:buster-slim"
php="8"
nginx="1.20.1"
support.t3kit="11"
support.typo3="11"
image.name="t3kit/11-php8-fpm-nginx-buster"

nproxy

Nginx proxy to use with t3kit project

Based on Automated Nginx Reverse Proxy for Docker

Use it to handle several t3kit projects in one local machine. The main advantage of it is just to use one VIRTUAL_HOST env variable to separate it from other projects

Setup

1. Clone this repository
2. cd nproxy
3. docker compose up -d - run nproxy using docker compose

---

mkcert

HTTPS Support for local development with Nginx proxy

We are using a Docker image to generate all needed keys and certificates. This image is based on mkcert tool. It is also possible to use it without docker image, but you will need to install this tool into your system. mkcert documentation

Setup

1. Create a folder on the host where we will store our keys and certificates.

   mkdir ~/.certs

2. Create local CA and generate locally-trusted certificates based on local CA

   • t3kit_first_setup - create a root certificate for a local certificate authority and generate locally-trusted certificates for *.t3.localhost wildcard domains.

   docker run --rm -v ~/.certs:/certs t3kit/mkcert:1.0.1 t3kit_first_setup

   Note: With this wildcard based certificate we can have any amount of third-level domain virtual hosts without creating new certificates.

   • add - generate .localhost based locally-trusted certificates

   docker run --rm -v ~/.certs:/certs t3kit/mkcert:1.0.1 add test

   It will create a locally-trusted certificate for test.localhost domain

   • generate custom locally-trusted certificates

   docker run --rm -v ~/.certs:/certs t3kit/mkcert:1.0.1 mkcert newsite.local

   It will create a locally-trusted certificate for newsite.local domain

3. Install local CA in the system trust store

   Import and trust a self-signed CA certificate

   macOS:

   cd ~/.certs/ && sudo security add-trusted-cert -d -r trustRoot -k "/Library/Keychains/System.keychain" "local_ca/rootCA.pem"

   Ubuntu:

   TBD

4. Configure the server to use the certificates.

---

Check t3kit starter kit with all needed documentation to start a new project on t3kit basis.