

What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
Hi!
The project is still active! I just haven’t needed to develop any updates because it’s currently stable, and the upstream Docker compose template, which is a reference for my project, hasn’t changed in 9 months:
https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml
Whenever Lemmy releases a new Docker container, it will just pull the latest one automatically. This will continue to be compatible indefinitely until the compose deployment (linked above) has any breaking changes added to it that I need to incorporate.
Thank you for the shout out :)
I use Backblaze B2, but stored in an encrypted Restic container, set up using this guide:
Restic has been great for automating backups, and even letting me mount the encrypted storage to grab individual files. I like doing it this way since I don’t have to trust Backblaze isn’t reading my data - I know for sure that they can’t.
Performance of storage that is both remote and encrypted is about what you would expect, but I don’t need access to the data unless something bad happens.
Ok… sure. But what physical devices would I use, and what software would they run?
Are there any “open” solutions to mesh networking that can compare to TP-Link Omada? I don’t think any open source hardware or software can come close, especially not for the newer Wi-Fi standards.
I haven’t bought them yet, but I’m seriously thinking about some Omadas. I imagine I can prevent them from phoning home, and the management software can run locally in a Docker container. Running it like that would be good enough for me even though they’re not “open.”
I’m planning a rework of my home Wi-Fi, and my current plan is an OPNsense box from Protectli, and a few EAP772’s:
https://www.tp-link.com/us/business-networking/omada-wifi-ceiling-mount/eap772/
If there’s something comparable/better that’s more of an open ecosystem, you definitely have my attention while I’m shopping around for different options.
Ah I see. I’ve gotten into some back and forth with the maintainer of Caddy about these build inconsistencies and lack of versioning, and he responded by locking issues on me… twice.
After that communication, I resigned to just keep things as they are because upstream is not willing to make the experience better for use cases like these.
He is impossible to work with, but Caddy is just really good :/