Selfhosted

39435 readers

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

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

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

submitted 1 year ago by [email protected] to c/[email protected]

28 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

[–] [email protected] 1 points 1 year ago (1 children)

I have four small computers that are the nodes, with a TerraMaster NAS for hosting the data.

I run Proxmox on all four nodes in a cluster. I've been moving things around in hopes of switching the hosts over to ZFS so two of the nodes currently don't have anythig on them. Eventually they will set up for HA fail over (the main driver for switching to ZFS). I have one VM running Yunohost. I have server LXC containers for some services and a couple running Docker that host the rest of the services. Basically as I found things I was interested in it was just easier and quicker to start with Docker. I'll probably move everything over to Podman and ditch the LXC containers and the VM. All in due time.

As for the hardware itself:

Node 1: Lenovo m93p: Core i5-4670 @ 3.4GHz; 16GB RAM; 256GB m.2 SSD
Node 2: Lenovo m93p: Core i5-4570T @ 2.9GHz; 16GB RAM; 256GB m.2 SSD
Node 3: Gigabyte Brix: Celeron J4105 @ 1.5GHz; 16GB RAM; 500GB m.2 SSD
Node 4: Trigkey Green G3: Celeron N5095 @ 2.9GHz; 16GB RAM; 500GB m.2 SSD
NAS: TerraMaster TNAS-5670. It has 2 drive bays with 2TB drive in each.

So far only a few items are accessible outside local network, those are hosted on the Yunohost VM. I am still learning how to set up a good reverse proxy and authentication. Once I get that figured out I will push for all Podman containers. I'm thinking about making use of ansible for "orchestration" with docker-compose files. Currently I don't monitor anything or collect logs.

[–] [email protected] 1 points 1 year ago (1 children)

You might check our Authentik for the authentication bit. It’s kinda complex, but can do proxy auth, OIDC, SAML, and LDAP.

[–] [email protected] 1 points 1 year ago

I've seen Authentik mentioned. I'm currently thinking about trying out Cosmos-Cloud.io. it has everything built in and runs on docker. I doubt I'll stay without since the licensing is ambiguous at the moment.