Ancestors

Written by slamp on 2025-02-01 at 22:31

The #infrastructure of #Hachyderm was discussed at #FOSDEM in a Birds Of a Feather. We talked about the different components and why they are structured as they are now, explaining both their history and the financial aspect.

In the photo below @hazelweakly and @esk ; @e_nomem and myself were also there.

=> View attached media | View attached media

=> More informations about this toot | More toots from slamp@hachyderm.io

Written by Emelia 👸🏻 on 2025-02-01 at 22:59

@slamp @hazelweakly @esk missed a set of nginx's between puma and cdn edge — buttons & fritz both have nginx to expose mastodon web (puma) to the CDN nginx

So:

Edge nginx -> Node nginx -> puma

Edge nginx -> streaming

=> More informations about this toot | More toots from thisismissem@hachyderm.io

Written by Esk 🐌⚡💜 on 2025-02-01 at 23:00

@thisismissem @slamp @hazelweakly yup - we were short on time even with an hour m, so we didn't hit quite everything 😅

=> More informations about this toot | More toots from esk@hachyderm.io

Written by Emelia 👸🏻 on 2025-02-01 at 23:03

@esk @slamp @hazelweakly I mean, theoretically we could tell mastodon-web (puma) to serve the static assets instead of using nginx for that since edge could cache those long term, but it's fine

=> More informations about this toot | More toots from thisismissem@hachyderm.io

Written by Eashwar on 2025-02-01 at 23:21

@thisismissem @esk @slamp @hazelweakly this also reminds me that we need to move the static assets to a separate domain so that we can cache it at the edge better. At that point it may not matter if we have nginx or puma serving up those files.

=> More informations about this toot | More toots from e_nomem@hachyderm.io

Written by Emelia 👸🏻 on 2025-02-01 at 23:37

@e_nomem @esk @slamp @hazelweakly I don't think Mastodon supports that?

=> More informations about this toot | More toots from thisismissem@hachyderm.io

Written by Emelia 👸🏻 on 2025-02-01 at 23:39

Oh, actually, CDN_HOST environment variable, didn't know about that

=> More informations about this toot | More toots from thisismissem@hachyderm.io

Written by Eashwar on 2025-02-01 at 23:41

@thisismissem yep, was about to link it but static.hachyderm.io should definitely be a thing

=> More informations about this toot | More toots from e_nomem@hachyderm.io

Written by Emelia 👸🏻 on 2025-02-01 at 23:43

@e_nomem I'm just not 100% sure how this would affect deployment of new versions? Would we back static.hachyderm.io with a bucket? Then have a step to copy public/ to that bucket?

=> More informations about this toot | More toots from thisismissem@hachyderm.io

Toot

Written by Amber (deilannist) on 2025-02-01 at 23:55

@thisismissem@hachyderm.io @e_nomem@hachyderm.io You could yes, presumably using a tool like rclone with them both entered as remote targets. Although... that sort of brings into question "why?". Assuming these are referring to stuff like hachyderm.io's logo, icons and other branding, wouldn't the point be to keep them separate? They aren't going to change much unlike user uploaded content. I think it'd be interesting to have some sort of version control backing your static assets. Not sure git is the answer here but presumably the workflow would be "commits a change -> approved -> some action invokes rclone to copy the newly changed asset and deploy it".

=> More informations about this toot | More toots from puppygirlhornypost2@transfem.social

Descendants

Written by Amber (deilannist) on 2025-02-01 at 23:55

@thisismissem@hachyderm.io @e_nomem@hachyderm.io never mind - i see this includes scripts served for mastodon's front end.

=> More informations about this toot | More toots from puppygirlhornypost2@transfem.social

Written by Eashwar on 2025-02-01 at 23:59

@puppygirlhornypost2 Yeah, it's not super clear but the 'assets' referenced here are the sort of things that get updated only when we update to a new version of mastodon itself. They're highly cachable

=> More informations about this toot | More toots from e_nomem@hachyderm.io

Written by Amber (deilannist) on 2025-02-02 at 00:03

@e_nomem@hachyderm.io Before I make an ass of myself further - Does the talk from earlier go into detail how you deploy new versions of mastodon? I am thinking that if you do continuous deployment it shouldn't be that hard to have a stage where you copy files like https://hachyderm.io/custom.css to the bucket used in serving these static assets?

=> More informations about this toot | More toots from puppygirlhornypost2@transfem.social