Community Standards
Where to get help and how to ask for it effectively.
Skyport is built in the open, and the project works best when reports, questions, and pull requests are clear and respectful.
Where to ask for help
Section titled “Where to ask for help”Use the right channel for the right type of issue:
- Discord for installation help, quick questions, and community discussion
- GitHub Issues for reproducible bugs and feature requests
- GitHub Pull Requests for code or documentation contributions
What makes a good bug report
Section titled “What makes a good bug report”Please include:
- the Skyport panel version
- the
skyportdversion - your operating system and version
- the steps required to reproduce the issue
- relevant log output
- whether the issue is panel-side, daemon-side, or both
Good support etiquette
Section titled “Good support etiquette”When asking for help:
- describe what you expected to happen
- describe what actually happened
- include exact error messages
- paste commands and logs as code blocks
- avoid screenshots of text when possible
Respect other operators’ time
Section titled “Respect other operators’ time”Self-hosting software means some troubleshooting is expected. Before posting, make sure you have checked:
- your reverse proxy configuration
- your database and Redis connectivity
- your daemon logs
- whether your panel and daemon versions match
Contributions
Section titled “Contributions”Documentation and code contributions are welcome. If you are submitting changes:
- keep them focused
- explain the problem being solved
- include enough detail for maintainers to verify the change
Support links
Section titled “Support links”- GitHub: github.com/skyportsh
- Discord: discord.gg/PUuezaSqkY