I prefer compose merge because my "downstream" services can propagate their depends/networks to things that depend on them up the stream
There's an env variables you set in .env so it's similar to include
The one thing I prefer about include is that each include directory can have its own .env file, which merges with the first level .env. With merge it seems you're stuck with one .env file for all in-file substitutes
Optiplex with an i5 8500. Before that was using a celeron that used like 6w max
Since switching my server to an x86 based platform, I'm not jumping back to arm any time soon. Maybe some day
I do this using a native Linux host so Google corals work right for my frigate security system. Windows vm is a qemu KVM with GPU passthrough, managed primarily through a web browser via cockpit https://qqq.ninja/blog/post/vfio-on-arch/
That's a crazy issue to have discovered. Maybe you could try a different reverse proxy like nginx to narrow down potential causes for the issue
Biuebubbles is based. I was running on an old Mac mini then switched to a vm on my server (spoofing the hw info from the Mac mini) for Ventura + lower power consumption.
I use an old iphone to link my phone number, but will eventually switch to pypush as a way or registering without the iPhone