this post was submitted on 30 Aug 2023
13 points (88.2% liked)

Selfhosted

61126 readers
406 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
13
Help me choose my setup, please! (lemmy.world)
submitted 2 years ago by spckls@lemmy.world to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

I have a server configuration to what i though would be best, and that is running a Debian, then installing a service i most frequently use, and use containers for other services. But, now i think that’s not a good solution and i’m looking for advice.

I thought of something like this:

Proxmox install Spin up a VM for this service that is currently running on Debian (can’t be in a container) Spin up a second VM, install Debian and Docker and install all other services as containers.

That would enable me to: a) backup the 1st VM to be able to deploy it if needed (backups) b) backup containers in the second VM so i can have them ready to be restored if needed

However, i’m not sure about setting it up like this. I’m worried if Jellyfin will work good as a container on a VM. Also, i’m worried about setting up nginx in a container on a VM, like, will it work as if installed on bare metal.

Other services i’m planning to run in containers on that 2nd VM are BookStack, Joplin, Mosquitto broker, Grafana, MariaDB, Influx DB, Studio Code, JellyFin, NectCloud etc.

The machine is a i3 1315U, 16GB RAM, 500GB SSD.

For the first VM i would allocate 2 cores and 4GB of RAM (that’s enough for what it does) and for the second VM (with all the containers) i would allocate the rest of the CPU and RAM.

Any advice is very welcome! Is proxmox still the best choice? Are there any other (better) choices? Is something obviously wrong with this setup?

you are viewing a single comment's thread
view the rest of the comments
[–] spckls@lemmy.world 1 points 2 years ago (1 children)

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?

[–] toma@lemmy.omat.nl 2 points 2 years ago (1 children)

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

[–] spckls@lemmy.world 2 points 2 years ago

Alright, yeah, i tend to overthink stuff to the point of not actually doing the thing i wanted. Thanks for the push!