02 / Blog
Notes from practice
This blog is my external memory. It collects solutions, questions, and those small technical light-bulb moments that usually appear shortly after the third failed attempt.
Restore production into staging without replaying external effects
A safe restore checks more than backups: it pauses writers, neutralizes pending work, and keeps mail and backup access out of staging.
A forced-command SSH boundary for a Codex worker
Why the Homepage worker reaches Codex only through aidev on the AI CLI server without turning SSH into general remote access.
Schema-valid AI jobs outside the TYPO3 request
How TYPO3 runs AI work as a bounded job, validates responses twice, and keeps slow processing outside the web request.
Staging ist eine Wiederherstellungsprobe, keine Kopie der Produktion
Eine belastbare Staging-Umgebung entsteht nicht durch einen weiteren Server. Sie beweist, dass sich Code, Konfiguration, Daten und Dateien kontrolliert wiederherstellen lassen – ohne Produktionszugänge, echte Benachrichtigungen oder unbemerkte personenbezogene Kopien mitzunehmen.
The dry run must be able to fail
A simulation is only valuable if it reflects the same contracts, states and error paths as the real integration. For TYPO3 projects, this results in a clear architecture: domain core, interchangeable adapters, controlled live tests and visible approvals.