xcjs

Ansible.

Infrastructure as code is the best documentation.

Ansible!

I second GitLab CI/CD - it’s a CI/CD system that just makes sense to me. That doesn’t mean it doesn’t have its complexities depending on your needs, but I’ve overall enjoyed my time working with it.

Sorry for spamming in this thread, but if you rely on Watchtower, there’s a maintained fork I recommend: https://github.com/nicholas-fedor/watchtower

Not for the latest and future versions of Docker.

This fork works, though: https://github.com/nicholas-fedor/watchtower

There’s a maintained fork, fortunately!

https://github.com/nicholas-fedor/watchtower

Thank you! That is exactly my point.

That’s not quite the same - that gives you the appearance of being a local device, which is enough to fool the restriction.

Their policy and technology enforcement is to charge for remote access, not relaying.

They charge for remote access whether it’s through their relay service or not, and you can’t opt out of fallback to their relay service.

The client is open source and can be administered using the open source Headscale server. I use it with Keycloak as an auth gateway.

It would be extremely barebones, but you can do something like this with Pandoc.

That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.

Macs aren’t the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.

Yeah, that’s why I started using .lan.

I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I’m certainly not going to switch to .internal unless another conflict surfaces.

I’ve also developed a host-monitoring solution that uses mDNS, so I’m not about to break my own software. 😅

It depends on the model you run. Mistral, Gemma, or Phi are great for a majority of devices, even with CPU or integrated graphics inference.

My go-to solution for this is the Android FolderSync app with an SFTP connection.

Of course!

The Docker client communicates over a UNIX socket. If you mount that socket in a container with a Docker client, it can communicate with the host’s Docker instance.

It’s entirely optional.

There’s a container web UI called Portainer, but I’ve never used it. It may be what you’re looking for.

I also use a container called Watchtower to automatically update my services. Granted there’s some risk there, but I wrote a script for backup snapshots in case I need to revert, and Docker makes that easy with image tags.

There’s another container called Autoheal that will restart containers with failed healthchecks. (Not every container has a built in healthcheck, but they’re easy to add with a custom Dockerfile or a docker-compose.)