-
Notifications
You must be signed in to change notification settings - Fork 155
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
Improve documentation on Capsule Proxy #640
Comments
hey @maxgio92, I can work on this, can you provide the resources from where the current users taking references for the "HOW TO" part so I can document it in a |
Great @wasup-yash, thank you! |
Thanks for the reference, I am currently understanding the Capsule-proxy landscape on how it fit into the picture for the new users and then we can work on the introductory guide for it, regarding this I have a question like we need to add the guide like apart from the current documented Capsule-proxy docs right? and also I have some suggestions like we can improve the current documentation of the Capsule proxy to get it more organized so we can work on it first and then we can create a guide, thoughts? |
Hey @wasup-yash, I don't have strong opinions. I think the current guide could be taken as starting point to be improved.
Then, the installation I think can be expanded. Going further, all of this could be part of a dedicated section I think, more than a single page - like now. In any case, I think it makes sense your suggestion, to start improving the organization of the current single-page one. |
yeah, it makes sense to improve the current docs part and then go on with the further use case guides and have dedicated sections if needed (if we need them) as I also discussed in the meeting today with @prometherion . |
This issue tracks the need to add details about how to use Capsule Proxy, specifically a user guide.
The guide could add details about how to communicate over the proxy, instead of directly to the API server.
As a proposal, a specific how-to guide could be added.
The text was updated successfully, but these errors were encountered: