paco

joined 1 year ago

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 1 week ago by [email protected] to c/[email protected]

4 comments fedilink

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

Old school self hoster: scared of the security challenges of modern hosting in c/[email protected]

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

I’m with you. Same vintage IT guy, self hosting similarly. I dunno. I throw a lot of stuff up on my xcp-ng box. Some is important. Some isn’t. I’m doing all manner of old-school firewall and perimeter security and not worrying a ton about logging in my containers. I guess I’m just fatalistic. If I get hacked to the point that I’m digging through logs to figure out what happened, I’m kinda fucked. So I focus more on backup and restore. Can I restore to a known good state? But I hear you. Kids these days with their containers and their pipelines and their devops. Back in my day…