Releases, security advisories, roadmap progress, and important community notices published by maintainers.
Open collaboration
Community
This is not another chat room you need to check every day. Searchable, durable discussions turn questions, deployment experience, and improvement ideas into answers the next user can reuse.
Start here on your first visit
A clear question, a sanitized configuration example, or real deployment feedback can all help the next user.
- 01Search first
Check the documentation, existing Discussions, and Issues for an answer or related work.
- 02Choose the right channel
Use Q&A for usage questions, Ideas for open proposals, and Issues for reproducible defects.
- 03Provide verifiable information
Include the version, system, architecture, command, and result, and remove credentials, private keys, domains, and customer identifiers.
Community entry points
GitHub Discussions
Day-to-day questions and open discussion live in the getclmbot organization Discussions. Use Q&A for usage questions, Ideas for adapters and features, and Issues for reproducible defects.
Introductions, use cases, and topics that do not yet belong in another category.
Feature ideas, upstream adapters, deployment targets, and experience improvements. A well-scoped idea may later become an Issue.
Community preference surveys. Results inform discussion but do not replace technical review or maintainer decisions.
Questions about installation, configuration, certificate discovery, and automatic updates. Mark the best answer after resolving the question.
Real deployments, sanitized configuration snippets, platform validation, and reusable operating experience.
What to discuss now
These topics are useful starting points and help maintainers understand priorities in real environments.
Which operating system, web service, and certificate source do you use? Which manual step do you most want to automate?
Describe the environment, operating mode, key configuration, and lessons learned. Remove domains, credentials, private keys, and customer information first.
Start with the problem, the people affected, and the desired outcome. You do not need a complete technical design.
Include the clmbot version, system architecture, command, expected result, and sanitized actual result.
