v0.7.1

Changelog

• Fixed bug that updated localStorage user when performing a user update even if the acting user wasn't the same.
• Added the --harmony parameter on start,sh fixing Node version compatibility issues with some modules (nodemailer)

v0.7.0

What's new

Node and API health checks

Konga 0.7.0 introduces health checks allowing you to monitor your Nodes and APIs state.
You can easily enable them for any Node or API from their respective pages.

Email Notifications

Administrators can be notified via email if a health check fails by enabling Email Notifications on the Settings page.

When Email notifications are enabled, Konga will send an email to all administrators the first time a health check fails and one every 15 minutes the API or Node stays down or unresponsive.

Keep in mind that "Notify administrators when" section in notification settings must also be configured respectively.

Note: The default sendmail transport for emails, is mainly for testing purposes and it's most likely that messages will end up in the junk folder. More email transports configuration will be available on upcoming versions.

Relative paths support

Konga now can run on relative paths without having trouble loading assets or connecting to socket.io.
For more details check out issue #27 .

Import/Export Snapshots

Node Snapshots can now be easily exported and imported to another Konga instance.

Docker volumes support / Default DB path changed

As from Konga 0.7.0 the default local db path is configurable (process.env.DB_PATH) and persistent in in it's own volume. Also the default db folder has changed from ./.tmp to /kongadata/.

That means that from now on, data won't be lost when upgrading Konga's container to a more recent version even when using the default filesystem db.

Note: In case you've been using the local db, you can easily migrate your previous ./tmp/localDiskDb.db by copying the file contents to the new /kongadata/konga.db file.

Minor fixes and UI improvements

Various UI elements have been improved and minor bugs have been addressed.

v0.6.9

Changelog

• Proper Certificates implementation
• Consumers can also be backed up with the Snapshots feature.
• Request Transformer Plugins can now be restored through Snapshots Feature (issue #62).
• Implemented data polling in the dashboard page (issue #61).
• Demo user can now define default connection although permissions are not fully implemented yet. It's best that you only use admin users for now (issue #60).
• Better error handling on profile updates (issue #59).
• Various minor fixes and improvements

v0.6.7

Changelog

• Fixed issue #52
• Fixed issue #54
• Various fixes and improvements

v0.6.6

Changelog

• Fixed issue: Can't edit consumer/api with custom user #49
• Fixed bower dependencies
• Various fixes and improvements

v0.6.5

Changelog

• Fix: Adding apis consecutively pre-populates fields with previous entry (issue #43)
• Fix: dashboard not updating when changing node (issue #41).
• Various fixes and improvements

v0.6.4

Changelog

• Changed user - node relation logic (see note).
• Active node version is taken directly from the Gateway info endpoint instead of the user created node.
• Fixed Bottom panel connection chooser (issue #41).
• Removed delete and update functionality from Upstreams.
• Various fixes and improvements

Note: This version introduces changes in Konga's database. See issue #40 on how they can be implemented.

v0.6.3

What's new

Connection chooser

As proposed by @PauloGDPeixoto at issue #37, a connection chooser is added at the bottom menu. Now, you're able to change active connections - nodes without the need to navigate to settings.

Snapshots (beta)

As proposed by @ksachdeva11 at issue #39, you can now take a snapshot of the currently active node.
All APIs, Plugins, Upstreams and Targets will be saved and available for later import.

This feature adds a new table to Konga's database so you will have to run the app, setting NODE_ENV environment variable to production once, as stated at issue #40 so that the migrations may be applied.

TAG based docker automated builds

From this version onward, TAG based automated builds are set up in docker hub so that you're able to pull and run a specific version of Konga if needed. Thanks @smazurov for the reminder at issue #35

Bug fixes

Various issues and minor bug fixes have been addressed.

v0.6.0

What's new

Kong version selection

Kong version is now an attribute of Kong node connection.

Kong 0.10.x support

Konga now supports upstreams, targets and the new SSL implementation logic.

Database integration

Konga now integrates with some of the most popular databases out of the box:

1. MySQL
2. MongoDB
3. PostgresSQL
4. SQL Server

See Readme for more information.

New consumer import adapters

API import adapter.

Mass import Consumers by issuing a GET request to an API endpoint.

Bug fixes

Various issues and minor bug fixes have been addressed.

v0.5.1

Kong 0.10.x compatibility

Implemented compatibility for Kong's 0.10.x APIs.