v0.5.0
Pre-release
Taking in account the issues that have been raised by the community, this version introduces breaking changes.
The goal is to simplify Kongas configuration, deployment process and deprecating some features in favor of using Kongs Admin API as is, without intermediate logic.
Changes
Frontend and Backend are merged
The loosely coupled backend and frontend logic, raised more issues than offered flexibility.
For that reason, they are not loosely coupled anymore. The GUI is served by the backend thus simplifying the overall configuration and deployment process, as well as enabling better Docker integration.
Consumers listing now uses Kongs Admin API directly.
Consumers as a listing concern, is a bit more complicated than APIs and Plugins. In most cases the number of registered consumers can get to thousands and Kongs listing API is very limited to that matter.
Kong's API doesn't provide sorting and text search functionality. Even pagination is difficult to handle without detailed meta info.
That is why Konga used to store the Consumers in it's own database as well and sync it with Kong, so that the listing could be handled appropriately.
That was a cool feature, but introduced complexity that led to issues.
For that reason, the intermediate logic layer is deprecated with the downside that listing is handled on the browser after loading all available consumers, until - and if - Kongs API becomes more "GUI friendly".
Docker Integration
The process of building a docker image doesn't need any previous actions and automated builds have been set up for all branches.
Bug fixes
Various issues have been addressed
Note
The application still uses It's own in memory data store for storing Kong nodes and Konga Users.
The downside of this method is that if Konga gets rebuilt, all created nodes and users will be lost.
Although it is very easy to fork the repo and apply your own persistence layer via sails adapters , I was wondering if it would be better to intergrate Konga with MongoDB, MySQL or Postgress out of the box. Feel free to open a discussion issue.