A #PHP developer who, in his spare time, plays #Tabletop and #VideoGames; if the weathers nice I #Climb rocks, but mostly fall off of indoor #Bouldering ones.

Pronouns He/Him
Blog https://realmenweardress.es
Photos https://pixelfed.social/pieceofthepie
Keyoxide https://keyoxide.org/606B2E3C103A443663DA82716B37390F365AADAA

  • 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: August 23rd, 2023

help-circle




  • Been using Mastodon a while. Once you hit critical mass of people you follow you just sort of find new ones.

    If someone you enjoy reading boosts something someone else has said you go off and probably end up following them too.

    With Mastodon you have to be a bit more pro active about building (and pruning) your social network but I’ve found it worthwhile.







  • The issue with orchestration is that you still need a way to share those small databases and config files.

    Docker has ok NFS support so you’d want to move the files to NAS shares and have them mount those. Without some way to centralise or spread the files out you won’t be covering your SSD failure case. Once you’ve got that going docker swarm will probably cover your needs just fine.

    You could go with K8S but based on you setup that’s a bit overkill (unless you’re doing it as a learning exercise, in which case go nuts).




  • Mmm. Looks like you’ve stumbled across (or at least highlighted) a bug in the way kbin federates out links in it’s content. I thought I’d covered the various cases but apparently didnt.

    When a post is made to kbin (or federated into it) that contains !magazineName@instance it does a best effort to make links that will work for users on that instance, but it appears that best effort applies to the outgoing federated content too - and it shouldnt, or at least, it should do something different.

    I’ll get a bug ticket in.

    EDIT. For now I’d recommend that where possible you use fully explict links i.e. [{@|!}community@instance](https://instance/{m|c}/community)