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
Thanks for the input. Do you think i will be running out of RAM in that configuration, like other commenters noted?
The reason I’d like to have two separate VMs is easier backups/restores, that way i don’t have to care about the phisycal machine, if i want to move to something else i only have to restore the VM.
As for the backups, i have one local backup on a separate machine (NAS) that gets backed up to an external drive, then another dedicated backup NAS that backups the first NAS and is otherwise disconnected from the internet, local network and power (turns on only once a week to backup), then another backup that backups the backup NAS to an off-site NAS, that also has an external drive making daily backups. Is that ok?
You would have 12 GB ram shared over all the dockers. I think you will be fine. Unless everything will be used intensively continuously. But that’s my opinion. Just give it a shot, nothing to loose. Promox itself does not take so much. So if it it does not run in this setup you need different hardware anyhow.
I don’t like the solution of running docker next to proxmox, not in a vm, you want proxmox to respond even if the docker vm is busy/overloaded.
In terms of backup you should be good. I would skip that weekly local backup construction, not sure what that adds if the off site backup is working reliable. I’ld format that one and add proxmox to it and make proper use of it (like a second docker vm)
I’m using 2GB RAM at this moment, not accounting for Jellyfin and Nextcloud, and i don’t have info about their load because they’re on a windows server. That’s all running bare metal.
The offsite NAS is at my office, and is serving my office needs daily, i just added a backup of my home server to it.
Do you have any idea how much cores/ram should i leave to Proxmox?
None. Just use everything in the VM’s. Yes that’s over committing, but who cares if the lead normally is reasonable and you can watch the ’summary’ in pm to see how the system is doing. Stop worrying, grab the proxmox iso and have fun
Alright, yeah, i tend to overthink stuff to the point of not actually doing the thing i wanted. Thanks for the push!