abed4/glpi repository overview

⁠GLPI Docker Image

A production-oriented Docker image for GLPI 11, built with PHP Apache, designed for clean deployments behind a reverse proxy such as Traefik, Caddy, or Nginx, with persistent storage and non-root runtime execution.

This image follows a structured storage layout for configuration, persistent application data, and logs, making it suitable for self-hosted environments and reusable public deployments.

GitHub repository:

https://github.com/Emusimbwa/glpi11-apache-docker⁠

---

⁠Features

• GLPI 11 based image
• Apache + PHP environment
• Designed for reverse proxy usage
• Persistent storage support
• Separate configuration, data, and log directories
• Support for downstream configuration
• Non-root runtime execution
• Suitable for Docker Compose deployments
• Compatible with external MariaDB database containers

⁠Storage Layout

This image uses the following directories:

• /etc/glpi for configuration
• /var/lib/glpi for persistent application data
• /var/log/glpi for logs

It also supports GLPI downstream configuration with:

• inc/downstream.php
• /etc/glpi/local_define.php

⁠Reverse proxy

This image is intended to run behind a reverse proxy.
For example, with Traefik, the container can be exposed through labels and routed over HTTPS.

⁠Database

This image does not include a database server.
Use an external MariaDB/MySQL container in the same Docker network.

---

⁠Example usage

Typical deployment includes:

• 1 GLPI container
• 1 MariaDB container
• 1 optional cron container using the same image
• 1 optional reverse proxy container managed separately

⁠Notes

Known vulnerabilities inherited from the official PHP base image may appear during scans.
They are monitored and will be reduced through regular rebuilds when upstream fixes become available.

• Sensitive values should be injected through environment files or Docker secrets
• Reverse proxy labels and domain names should be defined at deployment time
• This image is intended to stay generic and reusable, without hardcoded personal infrastructure settings