Selfhosted

40165 readers

1184 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:

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:

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Advice wanted: Combining current solutions into one home server (sh.itjust.works)

submitted 4 months ago by iAmTheTot@sh.itjust.works to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

I currently have a hodgepodge of solutions for my hosting needs. I play ttrpgs online, so have two FoundryVTT servers hosted on a pi. Then I have a second pi that is hosting Home Assistant. I then also have a synology device that is my NAS and hosts my Plex server.

I'm looking to build a home server with some leftover parts from a recent system upgrade that will be my one unified server doing all the above things in the same machine. A NAS, hosting a couple Foundry instances, home assistant, and plex/jellyfin.

My initial research has me considering Unraid. I understand that it's a paid option and am okay with paying for convenience/good product. I'm open to other suggestions from this community.

The real advice I'm hoping to get here is a kind of order of operations. Assume I have decided on the OS I want to use for my needs, and my system is built. What would you say is the best way going about migrating all these services over to the new server and making sure that they are all reachable by web?

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

[–] fruitycoder@sh.itjust.works -1 points 4 months ago (1 children)

K3s! You could even reuse your pis in the cluster.

I would deploy it to your new server, setup your CSI (e.g longhorn its pretty simple), find a helm chart for one of the apps and try deploying it.

[–] iAmTheTot@sh.itjust.works 1 points 4 months ago (1 children)

I understood like four of the words in your comment so I'm going to go ahead and assume that solution is too advanced for me.

[–] MigratingtoLemmy@lemmy.world -1 points 4 months ago

K3s is an embedded Kubernetes distribution by a Californian company called Rancher, which is owned by the Enterprise Linux Giant SUSE.

Kubernetes works on the idea of masters and workers. I.e. you usually cannot bring up ("schedule") containers (pods) on the master nodes (control nodes for brevity). K3s does away with such limitations, meaning you can just run one VM with k3s and run containers on top.

Although if Kubernetes is too hard I would push you towards Podman.

I do not know the extrapolation for CSI but Longhorn is a storage backend of Kubernetes for persistent storage across nodes