> For the complete documentation index, see [llms.txt](https://documentation.planeo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.planeo.dev/configuration-of-services/best-practices.md). # Best Practices While the key to Planeo is iteration, it can be helpful to know some best practices around the design of your Planeo resources 1. Avoid static port mappings unless you really need them. The more ports you have mapped statically to common numbers, the higher a chance you have of a port conflict 2. Create multiple Planeo Templates for each Helm chart to fit key use cases. You can define custom static values files with different settings for your Helm charts and expose specific and potentially distinct arguments to the Stack level. This allows your team to minimize Stack level configuration. 3. Leverage Planeobot to edit values templates. It has context on the default Helm values file and can help you discover and set key parameters. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.planeo.dev/configuration-of-services/best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.