I'm now thinking that instead of doing a bunch of Nginx nonsense in front of Pleroma I might instead submit a MR to Pleroma to make its static directory configurable, so you could just put soapbox-fe anywhere on the system then configure Pleroma to look at it.

I already have a working demo, just need to clean it up and submit the MR.

This should solve the problem for people who want to run a custom frontend with Pleroma.

Turns out this existed all along!

config :pleroma, :instance, static_dir: "/opt/soapbox-fe/public"

Boom, no special Nginx config required

This has actually happened multiple times now where I thought Pleroma was missing a feature and I actually discovered it while trying to add it. I was looking forward to contributing but I also can't complain. It's a good sign of they're 2 steps ahead.

@SandiaMesa Been messing with it, it's updated now

@SandiaMesa I changed it for compatibility with Pleroma. Same way, the files would just go in public/instance/about/*.html

@SandiaMesa You should probably fork my repo instead of just copying it so you can merge my changes