More in-depth docs.
closed
Ł
Łukasz Franikowski
Docs should contain more-in depth sections.
Generally I really like you docs, because they are concise and easy to read, so I don't want you to mess current docs with too much details which only small percentage of potential users will need, but some ADDITIONAL section with very low level details for each service would be very useful.
I'm using DO for about half a year now and I has to ask Support about details a few times, I don't remember all my questions but I had asked about ex.:
- App Platform http timeout
- Managed Databases connection pool config value server_request_query
- Grace period while stopping App Platform containers during deployment
It would be great if I could read about that details in some separated docs section.
John Mulhausen
closed
While I have to close this due to the lack of "exit conditions" (concrete proof that we have done something that 100% satisfactorily covers the complaint in all cases) I want to say we fully agree with this idea.
There are a few good places to look for such details. In general for miscellaneous value tables like limits, timeouts, and quotas, you should look on the front page of the product's documentation. For example, the feature comparison on App Platform has a lot of information about limitations here: https://docs.digitalocean.com/products/app-platform/#feature-comparison-by-tier
Another great place to look is in the reference area of our docs, such as the API documentation or in the doctl command-line tool's documentation. There are many commands there that can check account-specific and resource-specific limitations that affect you for the DO resources you've provisioned.
If there is any specific value you are not seeing or able to find, THAT is a great piece of feedback to give us so that we can cover that for you! It wouldn't get closed like this, it would instead be a very actionable and concrete request that we will be more than happy to help with in the docs. :)
Please let us know some values you have had trouble finding and we'll be sure to get them in. Thank you!
楊
楊家誠
