I’m not falling for that one again. Next you’ll tell me to use DeezOS
I’m not falling for that one again. Next you’ll tell me to use DeezOS
I don’t want to have remote access to my server outside of my home for security reasons, so this is just the bare minimum
What are your security concerns?
Yup, same experience. I started out hosting everything on a single box, but have slowly moved things like HA and Pi-hole to their own machines, so they don’t all go down when that one box goes down.
I was clearly being sarcastic.
There’s no real evidence that Meta was intentionally hiding anything, nor is Pixelfed even close to resembling a threat to Instagram.
So a few comments were hidden, no one seems to be able to reproduce it, and it appears to just be a glitch.
Why would Meta do this???
deleted by creator
My solution to this has been to not forward the ports on individual services at all. I put a reverse proxy in front of them, refer to them by container name in the reverse proxy settings, and make sure they’re on the same docker network.
Oh wow! Quite a journey!
I’d consider Paperless a hall-of-famer for self-hosted software and something most people who get into self-hosting discover at some point, even if they don’t use it.
So thanks for building it, even if you’ve moved on. You gave the forkers something great to build from.
Legend!
Do you use NGX yourself?
I recently tried out Cockpit on top of plain old Debian and it was really nice. You can manage VMs and whatnot, but it’s quite a bit more lightweight than Proxmox IMO.
But rebuilding a bare metal server properly compatimentized took me a few hours only, so is that really so important?
Depends on how much you value your time.
Compare a few hours on bare metal to a few minutes with containers. Then consider that you also spend extra time on bare metal cleaning up messes. Containers don’t make a mess in the first place.
Add it to your fstab
Well said.
The spirit of Self-Hosting is trying things and then asking specific questions when you get stuck (stuck includes having no luck using a search engine).
Sure, that’s great while it’s still just “instances that do federate with threads” and “instances that don’t federate with threads”.
I really don’t think that’s a meaningful comparison.
Federation relies on unity – fragmentation ruins that.
If you see massive fragmentation as a feature then I really don’t know what to tell you.
I guess enjoy?
Yup, thus fragmenting the crap out of the fediverse (the last E)
Sounds like opinions are pretty mixed. Maybe we should put it to a vote.
But then how do we decide if that vote should be public or not…