Heads up — packaged installers (XAMPP etc.) vs Docker for TicketsCAD

[Ronald Jones]

Hi all,

Just a "users beware" post to get people thinking, not a support request.

If you're running TicketsCAD on a packaged installer like XAMPP — which bundles PHP, Apache, and MySQL/MariaDB together — it's worth knowing those bundles don't always stay current. XAMPP for Windows hasn't had a mainline release since 8.2.12 on 2023-11-19. TicketsCAD is still supported on PHP 8.2.x, so for now things line up, but if TicketsCAD eventually moves past 8.2.x and the packaged installer you're using hasn't kept pace, you could end up stuck without a supported PHP version — no patches/fixes for future TicketsCAD updates unless you're comfortable manually swapping PHP yourself.

For what it's worth: PHP is replaceable inside an existing XAMPP install without a full uninstall/reinstall — you can swap the php folder and update the Apache config directly. I tried this myself and still ran into issues following a few guides, so it's not necessarily trivial even once you know it's needed.

That raises the real question: if a user wants to keep using XAMPP specifically but XAMPP stops shipping current PHP, what's the recourse? A few options as I see it:

1. Manually patch PHP inside the existing XAMPP install (doable, but fiddly, as above)
2. Switch to XAMPP-Lite, a community fork that stays on current PHP releases
3. Move to TicketsCAD's Docker image instead, which sidesteps being tied to any installer's update cadence entirely

Curious which of these (if any) people here have actually landed on, or if XAMPP/similar all-in-one installers are still common in the community despite this.

Thanks!