this post was submitted on 19 Sep 2021
4 points (100.0% liked)

Self Hosted - Self-hosting your services.

508 readers
1 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 3 years ago
MODERATORS
 

Sorry, maybe a weird question. But I am gonna acquire a nice server soon and am interested on how to manage that. I want to run stuff like a webserver, matrix server and just a lot of cool stuff. But how do I approach that on a software level? Any tips would be nice. Thanks

top 5 comments
sorted by: hot top controversial new old
[–] bananahammock@lemmy.ca 3 points 2 years ago

Docker-compose and a terminal is how I do it. Its simple and effective. I'm able to manage ~20 services that way.

[–] WigglingWalrus@feddit.uk 1 points 2 years ago

I use Unraid (an OS). Really liked it for the last few years I've had it.

[–] stoex@programming.dev 1 points 2 years ago

I run a Kubernetes cluster across 3 different servers (nodes) + one small control plane server.

[–] dleewee 1 points 2 years ago

Proxmox PVE gang. Excellent platform to self-host anything you could want to run from Windows/Linux VMs, LXC containers, Docker, or mix and match. The web GUI makes management easy and gives you a nice dashboard too.

[–] aexiruch@lemmy.ml 1 points 3 years ago

Professionally I am an "Architect" and not much involved in system config (anymore), what I describe below is how I do things for my own, private, servers: Not a big fan of docker, it too often means "cobbled together by a dev not understanding security implications" aka "Institutionalized 'works on my machine'" (of course there are exceptions!). Generally I like using Ansible, because it feels close to how I learned things (ssh, manually), while still making things reproducible (Infrastructure as Code). But, again, not too big a fan of using other peoples "roles", because you never know how well they actually understand what they're doing. I read them for a rough understanding, but usually opt to write my own, based on careful reading of a given software's config manual.