Running GLPI automatic actions from cron
Switching GLPI automatic actions to CLI mode with a per-minute cron, which actions to schedule (mail collection, notifications, SLAs) and forcing one action from the command line.

Keeping a self-hosted GLPI healthy: automatic actions, notification queues, backups, database growth and console maintenance tasks.
Switching GLPI automatic actions to CLI mode with a per-minute cron, which actions to schedule (mail collection, notifications, SLAs) and forcing one action from the command line.
Fixing GLPI emails that never leave: SMTP checks, the queuednotification action, oversized queued messages exhausting memory_limit and clearing the queue safely.
A complete GLPI backup: database dumps, the files directory minus cache and session folders, config keys, and a test restore before upgrades.
Reducing a bloated GLPI database: log retention per entry type, the PurgeLogs action, staged purges for software and user history and reclaiming disk afterwards.
When glpi_logs passes 5 GB: running pt-online-schema-change for engine and column migrations and index work without long table locks, and its risks.
Day-to-day administration from bin/console: maintenance mode during changes, system status checks, schema integrity checks and user management commands.

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.