Beta and feedback
Rigly is in public beta. It's ready for everyday use, and we use it ourselves, but you may find rough edges, and things will change as we hear from you.
What beta means
- Updates come often. Rigly checks daily and updates itself, so fixes reach you quickly.
- Your projects are safe. Rigly never changes your project files, except when you ask it to: creating a site, or a workspace's copy.
- Back up databases you care about. Rigly's databases are for local development. Keep a copy of anything you'd miss, as you would with any development tool.
- Some things may change, such as settings, commands and defaults, before version 1.0.
Send feedback
Bug reports, ideas and questions all go to Rigly's issue tracker on GitHub. You need a free GitHub account to post.
The quickest way is from Rigly itself: choose Help › Report a Bug… (or Suggest a Feature, or Ask a Question) while Rigly's window is open, Send Feedback (Beta) in the menu under Rigly's menu bar icon, or click the Beta badge in Rigly's window. Rigly opens the form with your Rigly and macOS versions already filled in.
Before reporting a bug, have a look at the open issues: someone may have reported it already. Add a 👍 to it so we know it affects you too.
A good bug report
- What you did, what you expected, and what happened instead.
- The output of
rigly doctor, which shows Rigly's checks. - Anything relevant from the Logs window. Remove anything private first.
- Other development tools on your Mac, such as Herd, Valet, MAMP or Docker, and whether you use a VPN.
The troubleshooting guide solves the most common problems, if you'd like to try first.