Swagger-ui not loading

[diogenes]

Trying the route /akkoma/swaggerui/ does not show swagger-ui

Installation:
./docker-resources/manage.sh mix pleroma.frontend install swagger-ui --ref stable

Admin-FE config:

Admin-Fe frontends:

Please help me troubleshooting. I am using the docker installation.

[ilja]

the endpoint isn’t working any more for some reason, see comment Newbie wuestion: how to view complete list of endpoints supported by Akkoma 3.5.0? - #9 by ilja

[diogenes]

Thanks! At least it works using the FE Picker. That’s something

[Oneric]

(now moved to the more fitting thread, sry)

From the other thread

@ilja

I’m not sure how to properly fix it, but I’ve been able to work around it, you can find it at https://ilja.space/pleroma/swaggerui/ (note that you need to also use the last slash).

For anyone who can spend the time looking further into this problem, it seems that the /akkoma route isn’t properly used for some reason + it also seems to need a slash at the end (at least I have to when using the pleroma route, as I have done now). Here’s the diff I did to get it working on /pleroma/swaggerui/

The issue is /akkoma is an API route prefix, so the frontend plug skips over the request. Ironcially the thing which makes /akkoma an API prefix is the frontend picker browser UI added in de64c6c while the preferred frontend override apparently (though no idea how) makes it accessible anyway?

[diogenes]

Maybe instead of the route /akkoma/swaggerui we change it to /swaggerui at least would be no conflits, right?

[ilja]

*oma allows profiles to be fetched on /<username>, so adding something directly on the root will 100% cause conflicts there. Imo that’s a behaviour that should’ve never gotten in, but that’s another discussion (which also kinda relates to #279 - Add /@<username> route - AkkomaGang/akkoma - Akkoma Development ).

[diogenes]

Maybe the better solution is to use an subdomain for other FE?