Manually serve the Swagger UI

[sebadob]

Hey,

I currently use the SwaggerUI in an actix-web application. After a lot of time spent trying to figure out why my application was using insane amounts of memory already in idle after a fresh start, I found out it actually was the SwaggerUI. The API has quite a few endpoints and the final actix service is almost 13MB. The big issue here is, that this is not wrapped in an Arc<_>, so when I spawn 16 HTTP workers, it adds 16x 13MB of memory just to serve API docs. I tried wrapping it in an Arc<_> manually, but it complained about the HttpServiceFactory not being implemented for Arc<SwaggerUi>.

Maybe I did not catch it if / how this is possible, but apart from that, I would like to do some very custom authentication stuff and only serve the docs to authenticated users against the application itself when specific conditions are met, to not leak complete API docs to people who should not know about it.

Is there a way to get a handle to the UI itself and serve the whole thing manually on a custom endpoint, and not use the auto-service impl for actix-web? This would solve both my issues, authentication and the insane memory usage.

[sebadob]

Sorry for the noise, I don't know why I did not see it earlier, but I found it:
https://docs.rs/utoipa-swagger-ui/9.0.2/utoipa_swagger_ui/fn.serve.html