Selfhosted

62310 readers

475 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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:

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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What does your infrastructure look like? (lemmy.world)

submitted 3 years ago by demosthenes@lemmy.world to c/selfhosted@lemmy.world

3 comments fedilink hide all child comments

In the What are YOU self-hosting? thread, there are a lot of people here who are self-hosting a huge number of applications, but there's not a lot of discussion of the platform these things run on.

What does your self-hosted infrastructure look like?

Here are some examples of more detailed questions, but I'm sure there are plenty more topics that would be interesting:

What hardware do you run on? Or do you use a data center/cloud?
Do you use containers or plain packages?
Orchestration tools like K8s or Docker Swarm?
How do you handle logs?
How about updates?
Do you have any monitoring tools you love?
Etc.

I'm starting to put together the beginning of my own homelab, and I'll definitely be starting small but I'm interested to hear what other people have done with their setups.

you are viewing a single comment's thread
view the rest of the comments

[–] ilikedatsyuk@lemmy.world 0 points 3 years ago (1 children)

I have an HP DL380 Gen8 and then a PC I bought from the local university and use as a server.

My DL380 runs ESXi. My PC runs Ubuntu on bare metal.

All of my apps are either fully VM-based (Home Assistant OS) or run in containers. Containers are far easier to build, upgrade, and migrate, and also make file management a lot easier.

I use Docker Compose. No Swarm or Kubernetes at this point.

Hopefully this is at least a good start! Let me know if you have any questions.

[–] demosthenes@lemmy.world 0 points 3 years ago (1 children)

Yeah, that's great! I've got an old HP desktop that a family member discarded that will be the start of mine.

Do you use a single docker-compose.yaml file for an entire machine, or docker-compose files per-app?

[–] ilikedatsyuk@lemmy.world 1 points 3 years ago

A combo of both. I group all my media apps like Sonarr, Radarr, SABnzbd, etc together in one compose since I consider each of them to be a part of the same “machine”, but most of my apps have their own compose.