vk6flab

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 unreadable … 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.

PHP is written in text files which can be managed using any number of version control systems. Pick your poison.

en.wikipedia.org/…/List_of_version-control_softwa…

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.

May I ask what you do with the failures?

For how much data?

What are you using to get it there and back?

I’m asking because I had been using this for years and only after a catastrophic event, discovered that my “helpful” backup software had turned on versioning which AWS, also helpfully, doesn’t explicitly tell you when you attempt to delete old backup sets, showing no objects but charging you anyway.

I did recover all my data after a catastrophic event, but it was an expensive experience to put it mildly.

Well, unless it came back in the last 25 minutes, it’s working fine in Western Australia.