Support
This page is for anyone who uses Vortex or is evaluating it and needs help. It lists where to get answers, from the documentation to the community and paid support, and explains how to report a bug or a security issue.
If you're new to Vortex, start with the Installation guide, then explore the Features.
🛟 Getting help
Self-help
Start here. These resources cover the common problems:
- 📖 Documentation - guides and references for every subsystem
- ❓ FAQs and Development FAQs - answers to adoption and day-to-day questions
- 🩺 Doctor - run
ahoy doctorto diagnose common local environment issues
A clean ahoy doctor run ends with
[ OK ] All required checks have passed. A failing check prints a [FAIL]
line, usually with a suggested fix, and stops the run there.
Community support
Talk to the community and follow the project's progress:
- Join the
#vortex-project-templatechannel in Drupal Slack to get help from the community and core maintainers - Use GitHub issues for bug reports and feature requests
- Track development progress on the project board
Professional support
If your organization needs dedicated support, DrevOps, the team behind Vortex, offers paid services:
- New project onboarding
- Migration of existing projects to Vortex
- Support plans with guaranteed response times
- Priority feature implementation
- Version updates and migrations
- Custom implementations
📧 Email: support@drevops.com
🚨 Reporting issues
Before you report a problem, do the following:
- Check the existing issues on GitHub
- Run diagnostics with
ahoy doctor - Review the FAQs for common solutions
- If you can, reproduce the problem in a clean environment
Include the following in your report:
- System information from
ahoy doctor info. The report redacts your username, IPv4 addresses, 36-characterID:values, and hex strings of 40 or more characters, but only in the binary paths and thedocker infooutput. Everything else stays as printed, including the operating system details and the host name thatdocker inforeports, so read the report before you post it - Steps to reproduce the problem
- Error messages and logs
- Your Vortex version, from the Vortex badge in your project's
README.md, and your configuration details
🔒 Security issues
Report security vulnerabilities by email to support@drevops.com, never in a public GitHub issue, so a fix can ship before the problem is public.
🤝 Contributing
The Contributing guide explains how to get involved.
💖 Supporting the project
Vortex is free and open source, and you can help keep it going:
- ⭐ Star the project on GitHub
- 📢 Spread the word to help others discover Vortex
- 💝 Make a one-time or recurring donation through GitHub Sponsors, or support the project on Patreon