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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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
typically you only need one power supply to run it, once you move to redundant power you can use the second one in case the first one fails. when you plug both in it will just balance across both until one fails.
in my opinion, hardware should only be hypervisors that run virtual machines, then you can provision VMs, similar to using VPSs. going this route you will need a vga monitor for initial setup, eventually everything is done over the lan with a web ui or ssh.
i use proxmox which is Debian based for the hypervisor.
As far as what you do with it, is that you can in theory replace the VPSs or test software in your lan.
to compare, i have my router (vyos), homeassistant, a docker server for hosting small services, a network lab (gns3), windows and mac VMs, and more running on a cluster that is using similar hardware.