To ease future upgrades of the Laravel framework, we had to sync up some of the internal configuration files. One of these changes has altered the setup of SQLite databases.
If you're using SQLite then follow these simple steps:
.envand copy the value of the the
DB_HOSTkey, if it's linking to a file.
- Create a new key named
DB_DATABASEand set the value to what
- Save the file, then run
php artisan config:cache.
So for example, if you previously had this:
You need to change it to this:
If you're interested in a TL;DR version, then here are the highlights!
Heavy use of metrics would previously slow down your Cachet installation — this is of no use when your customers are trying to see what's occurring!
We now the metric points with AJAX, after the status page has loaded.
The metric points API is now paginated.
Metric Point Data Type
The database type for metrics has been changed to
DECIMAL(15,3) which now allows for greater accuracy in your data.
Component Badges (Shields)
For example, in our demo instance this:
Will generate the following shield:
Subscribers are now able to manage their subscriptions. This page can be accessed through the link in any e-mails sent out from Cachet.
We've improved some of the details in the Cachet design. Including a refresh on the dashboard and login page.
Component groups are now split to better show them as individual items when collapsed.
Custom Headers & Footers
You can now supply custom HTML for both the headers and footers.
Please note that when supplying this code, the existing headers and footers will be hidden.
- API searching and sorting. The documentation has yet to be updated to reflect this change.
Numerous bug fixes have also been made in this release.
What's next for Cachet?
Alongside v2.2.0 we've been working on some new features, a couple of which you'll currently see in the Pull Requests page.
Refactoring Scheduled Maintenance
Currently Scheduled Maintenance is stored alongside Incidents. Whilst this works, it limits us in what we can do.
This refactor will:
- Store Schedules in their own tables.
- Affect multiple Components with one schedule.
- Potentially have recurring maintenance.
- Give Schedules a start and end date, it won't just expire.
- Single page to link to Schedules, useful for social media.
- API access!
This is probably the feature I'm most looking forward to as it'll redefine how you use Cachet and communicate incidents with your customers.
You'll be able to finally create the main incident, then add updates to it, without editing the original incident! This means that you'll finally have a proper timeline of updates, with API access and more.
A change like this requires modifications to the status page view, so expect some cool things to happen!
Improved Metric Point Storage
As we've found out with v2.2.0 a lot of metric points can affect the speed of your status page and whilst we've tried to avoid this, we can take it further.
Metric point values will now be grouped together if they're added with the same value in a customizable time-frame.
Essentially, you can store the same amount of points in less memory.
We'll also look at caching this data to make it faster all round.
Of course there is more, but we'll have to come back to that!