-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serving swagger.json from runtime mux? #230
Comments
https://grpc.io/blog/coreos/ has a pretty cool example of how to set up your swagger definitions on top of your API server. |
@johanbrandhorst That was actually really easy follow. Maybe I'll PR it into the README |
Show users how to combine these different projects in a unified way, e.g. how to serve the generated `swagger.json` on the API Closes #230
For anyone looking into this issue and finding the link is broken, apparently CoreOS changed their blogging system and now it's case sensitive! You can still find the post: https://coreos.com/blog/grpc-protobufs-swagger.html |
Thanks Francesc, I've updated my link 😄. |
Show users how to combine these different projects in a unified way, e.g. how to serve the generated `swagger.json` on the API Closes grpc-ecosystem#230
Updated the link again to https://grpc.io/blog/coreos/ |
It seems that the best practice for serving a swagger.json is to do it at the apex of the API. However, the runtime does not seem to easily support this.
Is there a best practice for this? Does it make sense to create a custom handler for the swagger here?
The text was updated successfully, but these errors were encountered: