by reading the docs im not so sure how to do it, here is my attempt

(ring/context
    "/docs" []
    ;:middleware [authorized-for-docs?]
    (docs/swagger-routes
     {:ui "/"
      ;:spec "/swagger.json"
      :data {:info {:title "Bla Bla"
                    :description "Bla Bla Bla Bla Bla o Bla"}}}))

but when i hit i get Can't read swagger JSON from

@plins looks right, I’ll try to see whats up with that.

ok… swagger.json path auto-resolution doesn’t work if it’s under a context. I think It should (all the reverse path info should be available), but it doesn’t seem to be implemented.

well, it can be set manually:

(context "/docs" []
     (docs/swagger-routes
       {:ui "/"
        :options {:ui {:swagger-docs "/docs/swagger.json"}}
        :spec "/swagger.json"
        :data {:info {:title "Bla Bla"
                      :description "Bla Bla Bla Bla Bla o Bla"}}}))

e.g. one can set all the possible options via the swagger-routes, which is kinda nice.

also those that effect the swagger-ui itself, for example adding {:options {:ui {:jsonEdit true}}} will cause all the body text-boxes to be rendered as forms.

here’s the full list of swagger-ui parameters: http://swagger.io/docs/swagger-tools/#customization-36

hope this helps.

and - please write an issue of that the :spec path auto-resolution doesn’t work under context.

done 🙂 thanks for he fast response