A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Okay #Plesk, I'm breaking up with you.
When I was new to #SysAdmin stuff, #Plesk helped me a lot with setting things up, especially email. But this is just stupid. I'm already paying for a server package that comes with Plesk, but it can't administer #PostgreSQL?
Fuck that. I'm leaving.
Any #OpenSource #FOSS alternatives? (Don't you dare to say #Docker π )
@[email protected]
@[email protected]
@[email protected]
#selfhosted #server #admin
@fell @[email protected] @[email protected] @[email protected] i don't know for sure if #podman is foss but i know it is an alternative to Docker.
Yep podman is FOSS. It was developed by redhat originally, which might be concerning to some given the recent news about RHEL, but that's probably not relevant. Use it for homeassistant, etc and it can be less ready-out-the-box than normal docker but works well on the whole. Mind you if you have an issue with docker-the-system rather than any docker.io controversy, then it probably isn't for you either.
@fell @[email protected] @[email protected] @[email protected] https://podman.io
@cmicmuir @[email protected] @[email protected] @[email protected]
Podman might be interesting, but I've had bad experiences with containers. If you compare them directly, there is a noticeable performance impact. At least with #Docker there was. And I don't want to pay for more hardware than I need. I'll give it a try, thanks!
The performance impact usually is negligible. Containers are nothing else than cgroups and a set of namespaces. In fact, you can create a container without any container runtime (podman, docker etc.). It might be that the performance hit was due to an image being built poorly, or the runtime being configured in a strange way? The only metric where there is some performance hit is the network, and that's because - depending on the configuration - the traffic **might ** flow through more hoops. Obviously it is possible to run the containers in the host network namespace, if this is really an issue.
All of this not to try to convince you or to claim your experience is false, is just that I am very surprised, I am aware that containers have some downsides, but usually performance is not really one of them.