this post was submitted on 12 Jul 2024
49 points (98.0% liked)

Selfhosted

39964 readers
339 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
49
Monolithic setup vs dedicated devices (feddit.org)
submitted 3 months ago by tjoa@feddit.org to c/selfhosted@lemmy.world
33 comments fedilink hide all child comments
 

Being a noob and all I was wondering whats the real benefit of having a monolithic lets say proxmox instance with router, DNS, VPN but also home asssistant and NAS functionalitiy all in one server? I always thought dedicated devices are simpler to maintain or replace and some services are also more critical than others I guess?

you are viewing a single comment's thread
view the rest of the comments
[–] WhyJiffie@sh.itjust.works 2 points 3 months ago

It could be a good idea to move more critical things to a different machine. It's often said that you shouldn't run your router and/or firewall on your main server, but I think there are also security reasons for that.

Or to move those to a low power consumption machine with cheaper hardwRe that are either more resource friendly, or very heavy but it's fine if they can only finish their task over a longer time.

Also, think about how could things go wrong. Have a second DNS and DHCP server (it's difficult to run a secondary DHCP besides the primary, maybe you don't need that), and some way you can reach the internet if the router or the firewall gets borked. That "way" does not need to be accessible at all times, but you should be able to switch it on when needed.
Don't forget to test that these are actually working after you have sweet them up.

Whatever you decide on, don't forget that you don't have to do everything at once. Don't let it overload you. Learning new tech takes time.