this post was submitted on 31 Oct 2026
164 points (98.8% liked)

Selfhosted

63507 readers
546 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Every Go application since 1.24 will activate MPTCP on their sockets by default.

And I've read that this includes Syncthing, which is why I'm posting this here

you are viewing a single comment's thread
view the rest of the comments
[–] mhzawadi@lemmy.horwood.cloud 6 points 2 days ago (1 children)

It took longer than planned as we are in the process of getting everything sorted for quick rebuilds, most of the time was waiting for GitHub to not poo it's self.

If we had everything in ansible it would be 5 minutes

[–] corsicanguppy@lemmy.ca 1 points 1 day ago* (last edited 1 day ago) (1 children)

If we had everything in ansible it would be 5 minutes

Ansible at the day-job takes about 45 min to do a patch. As someone who's used a fair number of alternatives, maybe consider anything else on the planet?

But, seriously. The response to this particular sploit wasn't really "config management"-y. It was a simple process that cron generally handled anyway, and network segregation and firewalling allowed us to prioritize easily. My worry is that there are some core architectural decisions you may need to revisit in the post-mortem on this, because there may be some fundamental changes required to get sensible wins in the future.

(If you're on containers, I weep for your validation challenges; also, get bazel)

[–] mhzawadi@lemmy.horwood.cloud 3 points 1 day ago

We find ansible to be the best way to manage our fleet, patching and keeping config in sync.

That's not to say it can't be slow sometimes, but it works for us.