~2 minutes reading 🕑

Fri, 10 June 2016

← Back to articles

Kinto-admin reaches 1.0

When choosing a database, it's a good idea to study a few important criteria: how nice is the API? Is it well documented? Will it scale? What is the tooling available? Tooling is especially important as it's what will make your life as a developer easier. We've been working on one specific tool, called kinto-admin, which wants to be to Kinto what phpMyAdmin is to MySQL. Today we're announcing the release of version 1.0.


In past releases you had to write and deploy a configuration file explicitly describing the resources to expose in the admin. Kinto-admin 1.0 now allows users to discover and browse the buckets, collections and records they have access to on a given Kinto server. They can also create, update and delete them, provided they have the required permissions. No need for configuration files anymore!

Collection settings are configurable from the admin, including defining their JSON schema and display options such as fields to render in the records list and the widgets to use to render form fields. These settings are stored in the collection metadata on the server.



For authentication, kinto-admin currently supports Basic Auth, and Firefox Account if kinto-fxa is installed on the server, though we're planning to add more providers in the future.

We've also added native support for kinto-attachments, which means you can attach files to records and post them to the server when the capability is available.


We really hope you'll enjoy this new version as much as we loved building it. You can use our hosted instance on Github, or – as kinto-admin is a pure html/css/js static Web application – host it on your own static Web server.

Of course there are and will be bugs, and you're invited to file new ones on the issue tracker. By the way, did I mention 1.0.1 is out already?

What's next?

We're planning to add the following major improvements in the near future:

  • Allow building collection JSON schemas using HTML widgets instead of entering raw JSON manually (we're fully aware this is not user friendly at all);
  • Allow managing permissions for buckets, collections and records;
  • Allow extending the admin by exposing a plugin API and a custom build system so you can tweak the way it renders and behaves;
  • When we get plugins, we have many ideas for them and a first exciting one is to provide metrics and charts. But hey, we're not there yet :)
Revenir au début