Stay up-to-date with news from the Flare team.
Errors will inevitably occur in your application. There is no way around it. If you notice them while working locally, you can fix them immediately. However, if your application is already live, it gets more tricky because you are not the only person triggering errors anymore. This is where error tracking software like Flare comes in handy.
Secret secrets are no fun, secret secrets hurt someone... unless they're managed right in your Laravel deployment! Say goodbye to plaintext perils and .env file follies. For Flare we explored some alternative solutions like config servers, the env:encrypt command and git-secret to keep your production environment variables safe and sound. Using git-secret's with user-specific access control and PGP encryption, managing environment variables becomes a breeze.
Good things are coming!
We're giving our entire service a new coat of paint
As of today, Flare can notify you via Telegram. In this blog post, you'll see that we didn't only provide basic support but also went all the way with notification actions.
Like most SaaS companies, the Flare back-office features a neat dashboard showing some of our key metrics. Using Laravel Nova it's pretty easy to aggregate data per model like the total number of errors or the active subscriptions per week. Behind the scenes these dashboard tiles and graphs use simple database queries. For example, the number of active subscriptions is a simple
SELECT COUNT(*) query on the
subscriptions table. But how do we query new subscriptions per week?
We've added a nice addition to your UI.
Like many others SaaS applications, you can try out Flare using a trial period. Of course, not everybody that tries out Flare will convert. After the trial period is over, some people will not use the service anymore. In this post you'll learn how we clean up the data of inactive teams and users