Open Collective
Open Collective
Dokku 0.20.x and skunkworks projects
Published on April 5, 2020 by Jose Diaz-Gonzalez

I wrote a longer public blog post that explains things in more detail.

With the release of 0.20.x, I'll be refocusing on a few core areas of improvement:

  • Security Improvements
  • High Availability through Kubernetes and Nomad
  • Cloud Native Buildpack support

In addition, I'm starting active development on a couple interesting projects:

  • dokku-api: This will be a golang-based web server that will enable access to common tasks performed on dokku servers via json-api. This will make it very easy for folks to integrate it with popular frontend frameworks such as Ember, React, and Vue.JS to create excellent web interfaces, but also enable richer client-side apps. Additionally, it will include a way to push code via http(s), which will both enable folks in more restricted environments to use Dokku more easily, but also ease usage of the Dockerfile-based installation method (no one wants to export port 3022).
  • team management: When I first took over Dokku development in 2014, I really wanted to use Dokku as a solution for app management at a university for quite a few student developers. Unfortunately, you'd definitely want tighter controls over who gets access to what, and Dokku isn't super-well equipped for that. The existing dokku-acl plugin isn't scalable and doesn't integrate that well with other plugins. I recently wrote a doc outlining what such a team plugin might look like, and it might be something that I finally have space to tackle. It's not clear to me whether I'll release these as opensource or not, but it will likely be offered as a benefit to higher-tier patrons at first.

Looking back at the 0.3.0 docs, we outlined three things Dokku would not do:

  • Multi-host. Not a huge leap, but this isn't the project for it. Have a look at Deis.
  • Multitenancy. It's ready for it, but again, have a look at Deis.
  • Client app. Given the constraints, running commands remotely via SSH is fine.

Quite funny to me that all of these problems are finally being tackled in some form (also, RIP Deis). That said, I'm definitely looking forward to the next few months as we gear up for the 1.0!