Selfhosted

40152 readers

500 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

So what are #FreeBSD folks doing for multi-node, high availability file systems? I looked at #Gluster, but that doesn't work. I'm starting to look at #minio, but it's an S3-oriented API. (fedia.io)

submitted 2 months ago by paco@fedia.io to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

I'd like to get to a docker swarm sort of situation where I have 3 identical docker VMs, running 3 identical Caddy configurations, with 3 identical Apache VMs, and requests load balanced across them. And then I want a shared filesystem so the users can upload the files for their web sites to one location, and it's made available to all the web front ends.

I'm currently in a mixed environment:

```
#xcpng on bare metal
```

FreeBSD VMs running important services (bastions, email, DNS)

#AlpineLinux VMs running docker for all my container-based stuff

So I'm trying to do the shared, highly available FS part of this design and I'd stay with FreeBSD if I could. #selfhosted

top 4 comments

sorted by: hot top controversial new old

[–] just_another_person@lemmy.world 13 points 2 months ago (1 children)

I think you're doing this on hard mode. K8s and Longhorn gets you what you want.

You could try Ceph in your setup, but you're going to run into issues if your environments aren't all exactly the same.

[–] possiblylinux127@lemmy.zip 2 points 2 months ago

K3s is lighter and less complex

[–] Overspark@feddit.nl 5 points 2 months ago

Object storage (the S3 API stuff) is the most logical answer here, it's much simpler and thus more reliable than solutions like Gluster, and the abstraction actually matches your use case. Otherwise something like an NFS share from a central fileserver works too.

But I agree with the other comment that you're trying to do kubernetes on hard mode and most likely with a worse result.

[–] possiblylinux127@lemmy.zip 2 points 2 months ago

FreeBSD isn't going to have the same support as Linux.

Under Linux you could use Ceph or even garage object storage. There are plenty of other options. Maybe you could try to get Linux stuff working on BSD.

Alternatively you could setup a highly available NFS share.