Selfhosted
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:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Sorry I can't help with the proxmox stuff but it is absolutely fine to have a qcow2 image on an SSD pool. Modern SSD write endurance is so high as to be a non issue especially in the relatively tiny work loads that HA will put on it
I think the problem is that ZFS expects zvols and qcow2 is adding an additional layer on top and this is increasing the wear and tear of the disks especially SSDs and eventually it is not recommended. Plus qcow2 I think is better for virtualisation.