Skip to main content
We’re here to help you get the most out of Aurora. There are several ways to get support, report issues, and connect with the community.

​
Documentation

Before seeking support, check if your question is answered in the documentation:

​
Community Support

​
GitHub Discussions

Join the conversation on GitHub Discussions:
  • Ask questions and get help from the community
  • Share ideas and feature requests
  • Discuss best practices and use cases
  • Show off your Aurora setup

​
GitHub Issues

Report bugs and track feature requests on GitHub Issues: Before creating an issue:
  1. Search existing issues to avoid duplicates
  2. Check the Troubleshooting guide
  3. Gather relevant information (logs, configuration, environment)
When reporting a bug:
1

Describe the issue

Provide a clear and concise description of what the bug is.
2

Steps to reproduce

List detailed steps to reproduce the issue:
  1. Go to ’…’
  2. Click on ’…’
  3. See error
3

Expected behavior

Describe what you expected to happen.
4

Actual behavior

Describe what actually happened.
5

Environment details

Include:
  • OS and version (e.g., Ubuntu 22.04, macOS 14.0)
  • Docker version: docker --version
  • Docker Compose version: docker compose version
  • Browser (for frontend issues)
  • Aurora version or commit hash
6

Logs and errors

Attach relevant logs:
make logs > aurora-logs.txt
Or specific container logs:
docker logs aurora-server-1 > server-logs.txt
docker logs aurora-frontend-1 > frontend-logs.txt
Redact any sensitive information (API keys, tokens, credentials).
7

Screenshots

If applicable, add screenshots to help explain the problem.
When requesting a feature:
  1. Use Case: Describe the problem you’re trying to solve
  2. Proposed Solution: Your suggested approach
  3. Alternatives: Other solutions you’ve considered
  4. Additional Context: Any other relevant information

​
Contributing

Want to contribute code, documentation, or other improvements? We’d love your help!
  1. Read the Contributing Guide
  2. Read the Code of Conduct
  3. Fork the repository and create a branch
  4. Make your changes
  5. Submit a Pull Request
Types of contributions we welcome:
  • Bug fixes
  • New features
  • Documentation improvements
  • Performance optimizations
  • Test coverage improvements
  • Code refactoring
See the Contributing Guide for detailed instructions on:
  • Development setup
  • Branch naming conventions
  • Pull request process
  • Code style guidelines
  • Testing requirements

​
Direct Support

​
Email

For sensitive issues, security concerns, or private inquiries, contact the Aurora team: [email protected] Please use email for:
  • Security vulnerabilities (do not post publicly)
  • Code of Conduct violations
  • Partnership and collaboration inquiries
  • Enterprise support questions

​
Response Times

Please note that Aurora is an open source project maintained by a small team:
  • GitHub Issues/Discussions: We aim to respond within 1-3 business days
  • Pull Requests: Initial review within 3-5 business days
  • Email: Response within 1-2 business days for urgent matters
Response times may vary based on complexity and maintainer availability. Community help is always appreciated!

​
Code of Conduct

All community interactions are governed by our Code of Conduct. We pledge to make participation in our community a harassment-free experience for everyone, regardless of:
  • Age, body size, disability
  • Ethnicity, gender identity and expression
  • Level of experience, education
  • Nationality, personal appearance, race
  • Religion, sexual identity and orientation
Expected behavior:
  • Be respectful and inclusive
  • Give and accept constructive feedback gracefully
  • Focus on what’s best for the community
  • Show empathy towards others
Unacceptable behavior:
  • Harassment, trolling, or derogatory comments
  • Personal or political attacks
  • Publishing others’ private information
  • Other conduct inappropriate in a professional setting
Reporting violations: Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to [email protected]. All complaints will be reviewed and investigated promptly and fairly.

​
Security Issues

If you discover a security vulnerability, please do NOT open a public issue. Instead, email [email protected] with:
  1. Description of the vulnerability
  2. Steps to reproduce
  3. Potential impact
  4. Suggested fix (if any)
We take security seriously and will respond promptly to verify and address the issue.

​
Additional Resources

​
Documentation

​
External Tools

​
Development References

​
Stay Updated

Watch the GitHub repository to get notified about:
  • New releases and features
  • Important announcements
  • Security updates
  • Community discussions
Click the “Watch” button and choose your notification preferences.

​
Thank You

Thank you for using Aurora and being part of our community! Your feedback, bug reports, and contributions help make Aurora better for everyone. Whether you’re reporting a bug, requesting a feature, or contributing code, we appreciate your involvement in the project.

Build docs developers (and LLMs) love

Get started for freeTalk to us