

PHP is written in text files which can be managed using any number of version control systems. Pick your poison.
https://en.wikipedia.org/wiki/List_of_version-control_software
As someone else said, you can document your patches with a Docker file, but you’ll still need to track your changes.
Ultimately, what you’re essentially doing is maintaining a local fork of the code and keeping it synchronised with upstream.



I moved from VMware Fusion after a hardware failure and migrated to Proxmox. I use VMs to isolate client information and to test and use different OS versions and distros.
I have a VM that runs Docker and connect to it via SSH for running applications I don’t want to install on my main workstation.
My main workstation is also a VM.
I came from bare metal Linux for years and found that I spent too much time recompiling kernels to make it work with my hardware.
Now that everything is a VM, changing underlying hardware, and even hypervisor is trivial.
If VMware hadn’t been bought by Broadcom and allowed me to virtualise x86 on Apple Silicon, I’d still be running VMware Fusion. UTM by the way is completely unreliable … I really tried.
As it is, I’m running Proxmox on AMD.
in summary, Proxmox allows me to build what I need when I need it virtually and it’s running on a standard Debian host.
Edit: #$#__# autocorrect (unreadable -> unreliable)