Running GLPI in Docker with the official image
Deploying GLPI with the official Docker image and compose stack: environment variables for MySQL, persistent volumes, upgrades by image tag and production settings beyond the quick start.

Installing and sizing self-hosted GLPI: requirements, Docker and Linux installs, web server layout, directories, database replicas and caching.
Deploying GLPI with the official Docker image and compose stack: environment variables for MySQL, persistent volumes, upgrades by image tag and production settings beyond the quick start.
A production GLPI install on Ubuntu: PHP extensions, Apache virtual host on the public directory, MariaDB, timezone grants, cron and moving data directories out of the web tree.
Serving GLPI from Nginx with PHP-FPM: routing every request through public/index.php, blocking direct access to other paths and session cookie settings for HTTPS.
Placing GLPI configuration, the files directory, logs and the marketplace outside the source tree with downstream.php and local_define.php, and file permissions for each.
Sizing GLPI when thousands of agents report in: separate inventory and user front ends, a dedicated database server, NFS for shared files and load balancing in front.
Adding MySQL or MariaDB replicas to GLPI for reports, search and read-only fallback, the sync check options and the risk of stale results when always using the replica.
Configuring GLPI's cache backend with glpi:cache:configure, choosing Redis or Memcached for multi-server installs and clearing caches after upgrades.
Database versions per GLPI release, InnoDB buffer pool and temporary table settings Teclib suggests for busy instances, and keeping web to database latency low.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.