Who uses dokku and for what purposes?

[josegonzalez]

Would be nice to get an idea of what our community looks like so we can better prioritize upcoming features/build out things that would be useful to our users.

If you can, please fill out the following (omit anything you want):

• Version of dokku you use:
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
• Company Name:
• Size of team using dokku:
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):
• Primary use of dokku (staging env, local test, production):
• Where you host dokku (AWS/Linode/Digitalocean):
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks):
• Number of servers hosting dokku:
• Best current feature you love about dokku:
• The worst thing ever about dokku (please be specific, and file issues if necessary!):
• Something you'd love to see in the near future for dokku:
• How can we contact you for feedback (twitter, email, etc. please add contact info to github if that is your choice):
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):

Note that while we do take a look at this list every so often, it's worth creating an issue for anything you think can be improved with Dokku. 😃

For those out there who have complaints/suggestions for Dokku who may not wish to file an issue just yet, please contact my on IRC/slack. My nick is savant.

---

For those of you wanting to contribute monetarily to Dokku's development, you can do so on OpenCollective here. This will allow the core devs to spend more time writing features and improving the overall Dokku experience. Any and all amounts help :)

[trevormerritt]

• Version of dokku you use: 0.4.12
• Non-core plugins you use:
  • mysql
• Size of team using dokku:1
• Primary role of the dokku maintainers at your company: Dev/Ops
• Primary use of dokku (staging env, local test, production): CD, Production use on next major iteration of current major project
• Where you host dokku: Debian 8.2 on a VMWare host at work, Debian 8.2 on Proxmox host at home.
• How you deploy dokku : script from the dokku site.
• Best current feature you love about dokku: git push <dokku_repo>
• The worst thing ever about dokku:
  • no web based 'dashboard'
• Something you'd love to see in the near future for dokku:
  • a web based 'dashboard'
• If not lactose intolerant, what your favorite milkshake is:
  • The one that brings all the boys to the yard.

[michaelshobbs]

• Version of dokku you use: 0.4.4
• Non-core plugins you use (including internally developed ones):
  • dokku-app-configfiles
  • dokku-app-predeploy-tasks
  • dokku-app-user
  • dokku-apt dokku-deployment-keys
  • dokku-hostkeys
  • dokku-hostname
  • dokku-logging-supervisord
  • dokku-persistent-storage
  • dokku-slack
• Size of team using dokku: 5
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):dev
• Primary use of dokku (staging env, local test, production): staging/production
• Where you host dokku (AWS/Linode/Digitalocean): AWS
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): OpsWorks
• Best current feature you love about dokku:
  • plugin architecture
• The worst thing ever about dokku:
  • supporting nginx-vhosts

---

Note: We've since updated the nginx-vhosts support in 0.5.0 to be more rigorously tested and flexible in it's handling of various use cases.

[mlavin]

• Version of dokku you use: 0.4.12
• Non-core plugins you use (including internally developed ones):
  • dokku-postgres
  • dokku-opbeat
  • dokku-rabbitmq
  • dokku-letsencrypt
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): dev
• Primary use of dokku (staging env, local test, production): staging/production
• Where you host dokku (AWS/Linode/Digitalocean): VPS
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Ansible
• Best current feature you love about dokku:
  • plugin community
• The worst thing ever about dokku:
  • debugging bad deploys or broken upgrades (dokku or plugin)
• Something you'd love to see in the near future for dokku:
  • resolution on docker-swarm support (maybe just documentation of known caveats)

[jvanbaarsen]

• Version of dokku you use: ranges from 0.4.6 to 0.4.13
• Non-core plugins you use (including internally developed ones):
  • dokku-postgres
  • dokku-redis
  • dokku-mysql
  • dokku-elasticsearch
• Company Name: Firmhouse / Intercity
• Size of team using dokku: 4
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Dev
• Primary use of dokku (staging env, local test, production): Staging and production
• Where you host dokku (AWS/Linode/Digitalocean): Digitalocean and Transip.nl
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): via intercity (https://github.com/intercity/intercity-next)
• Number of servers hosting dokku: 5
• Best current feature you love about dokku:
  • The ease of which you can attach services
  • the ease of use for the CLI.
  • how easy it was for me to create a web dashboard surrounding Dokku :-)
• The worst thing ever about dokku:
  • Single server support
• Something you'd love to see in the near future for dokku:
  • Better support for backups (Apps and Dokku)
• If not lactose intolerant, what your favorite milkshake is:
  • That is confidential

[madflow]

• Version of dokku you use: 0.4.12
• Non-core plugins you use:
  • hostkeys-plugin
  • deploymentkeys-plugin
  • http-auth
  • pre-deploy-tasks
• Company Name: Priotas
• Size of team using dokku: 1 (as admin)
• Primary role of the dokku maintainers at your company: dev
• Primary use of dokku: dev env, in house production for services like "Hubot", "Mkdocs", "Huginn"
• Where you host dokku: Digitalocean
• How you deploy dokku: DO Droplet picker (Manual upgrades)
• Number of servers hosting dokku: 1
• Best current feature you love about dokku:
  • The plugin architecture
• The worst thing ever about dokku:
  • I found it hard to setup our distributed production system for testing (postgres, rest-api, frontend-layer, smtp server, ELK Stack, shared Volumes ...). I found this a lot easier with just docker-compose
• Something you'd love to see in the near future for dokku: ...
• If not lactose intolerant, what your favorite milkshake is:
  • The beer kind

[nielsonsantana]

• Version of dokku you use: 0.4.12
• Non-core plugins you use (including internally developed ones):
  • dokku-apt
  • dokku-volume(I used, but using docker-options right now)
  • dokku-deploy-hooks(my fork)
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Dev/Ops
• Primary use of dokku (staging env, local test, production): staging and production
• Where you host dokku (AWS/Linode/Digitalocean): Digitalocean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): manually through git
• Number of servers hosting dokku: 2 (one staging, one production)
• Best current feature you love about dokku:
  • Just Work!
  • SSL wildcard support;
• The worst thing ever about dokku:
  • Setup the application; Will be great there a script to centralize all configs (used in the plugins, like mount a volume, setup domain, environment variable) and deploy at once
• Something you'd love to see in the near future for dokku:
  • Better support for backups and deploy/integration(between applications).
  • I don't feel comfortable using plugins for postgres/redis. I install those applications on host server and access them from my application on dokku.

[Corstiaan84]

• Version of dokku you use: 0.4.5
• Non-core plugins you use (including internally developed ones):
  • dokku-postgres
  • dokku-mariadb
• Company Name: Fluxmatix
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): founder + developer + some devops
• Primary use of dokku (staging env, local test, production): currently staging, production when launching next app
• Where you host dokku (AWS/Linode/Digitalocean): DO
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Droplet
• Number of servers hosting dokku: 1
• Best current feature you love about dokku:
  • ease of deployment
  • ease of creating and linking apps
  • provisioning db's with plugins
• The worst thing ever about dokku:
  • If something breaks, the issue requires a lot of research generally
• Something you'd love to see in the near future for dokku:
  • a backup plugin that dumps db's, uploads to s3 or another service. Same for folders and perhaps whole apps?
• If not lactose intolerant, what your favorite milkshake is:
  • banana

[u2mejc]

Mine essentially matches Michael's, although I think he's being modest on the number of team members using dokku. Below are my personal uses, just food for thought I guess.

• Version of dokku you use: master (pulled multiple times daily)
• Non-core plugins you use (including internally developed ones):
  • Storage (it's not merged, so it's not core yet!)
  • Others I wrote
• Size of team using dokku: me
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): ops/dev
• Primary use of dokku (staging env, local test, production): local test
• Where you host dokku (AWS/Linode/Digitalocean): AWS, Virtualbox
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Opsworks, Vagrant
• Number of servers hosting dokku: multiple
• Best current feature you love about dokku:
  • The ease of heroku with the flexibility of aws. But I bet dockerfiles will be the future.
• The worst thing ever about dokku:
  • The difficulty describing exactly what Dokku is to a new user.
• Something you'd love to see in the near future for dokku:
  • Rollback to previous container
  • maybe we can make a more public roadmap?
• If not lactose intolerant, what your favorite milkshake is:
  • I could teach you, but I'd have to charge. 😄

[petewest]

• Version of dokku you use: 0.4.13
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • mysql
  • postgres
  • redis
  • root-cas (own development to inject internal trusted root CA certs at pre-build)
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): ops/dev/etc
• Primary use of dokku (staging env, local test, production): Staging, production, DR
• Where you host dokku (AWS/Linode/Digitalocean): Internal vSphere
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Internal Chef
• Number of servers hosting dokku: 3
• Best current feature you love about dokku:
  • encapsulation of dependencies (no more RVM!)
  • ease of deployment workflow
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • Vanilla!

[fruitl00p]

• Version of dokku you use: 0.4.13
• Non-core plugins in use:
  • dokku-letsencrypt
  • dokku-redis
  • dokku-mysql (and dokku-mariadb)
  • dokku-hostkeys (and dokku-deploymentkeys)
• Company Name: Kingsquare
• Size of team using dokku: 4
• Primary role of the dokku maintainers at your company: developers (=everyone)
• Primary use of dokku: development + staging + production
• Where you host dokku: internally + VPS provider (TransIP)
• How you deploy dokku: custom scripting
• Number of servers hosting dokku: 5
• Best current feature you love about dokku:
  • ease of use with new environments
• Something you'd love to see in the near future for dokku:
  • multi-host setup using swarm without the added complexity of etcd/zookeeper etc (i.e. scaling app to multiple hosts)
  • I'd also like to see easier rollbacks to previous releases (something like Rolling back app to previous deploy #553)

[Subtletree]

• Version of dokku you use: 0.4.13
• Non-core plugins in use:
  • dokku-postgresql
  • dokku-wkhtmltopdf
  • dokku-maintenance
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company: Developer
• Primary use of dokku: Staging, production
• Where you host dokku: Digitalocean
• How you deploy dokku: Manually through git
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • Ease of use
  • plugins
  • good documentation
• Something you'd love to see in the near future for dokku:
  • Documentation on how to go about troubleshooting an unknown problem/crash

Thanks for your work guys, loving dokku!

[pmclanahan]

• Version of dokku you use: latest (0.4.14)
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • dokku-letsencrypt
  • dokku-redis
  • dokku-postgres
  • dokku-memcached
• Company Name: just me
• Size of team using dokku: just me
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): it's really just me
• Primary use of dokku (staging env, local test, production): stage and prod
• Where you host dokku (AWS/Linode/Digitalocean): DO
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): your bootstrap script
• Number of servers hosting dokku: 1
• Best current feature you love about dokku:
  • letsencrypt
• The worst thing ever about dokku:
  • scaling will be tough at a certain point
• Something you'd love to see in the near future for dokku:
  • I'd like to see it stay much as it is now. It will cease to be good at what it is if it gets too much more fancy.
  • maybe better logging options.
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • Chocolate Peanut-butter

[ebeigarts]

• Version of dokku you use: latest (0.4.14 - 0.7.2)
• Non-core plugins you use:
  • mlomnicki/dokku-deploy-hooks
  • ribot/dokku-slack
  • mak-it/dokku-volume (will switch to storage when available)
  • dokku/dokku-postgres
  • dokku/dokku-mariadb
  • dokku/dokku-mongo
  • dokku/dokku-redis
  • dokku/dokku-memcached
  • dokku/dokku-elasticsearch
  • dokku/dokku-redirect
  • dokku/dokku-letsencrypt
• Company Name: makit.lv
• Size of team using dokku: 13
• Primary role of the dokku maintainers at your company: me, cofounder
• Primary use of dokku: demo, production
• Where you host dokku: DigitalOcean, VPS
• How you deploy dokku: sprinkle or manually
• Number of servers hosting dokku: 5
• Best current feature you love about dokku:
  • git push
  • dockerfile
  • isolation
  • zero-downtime deploys, plugins
• The worst thing ever about dokku:
  • network!? related build failures
• Something you'd love to see in the near future for dokku:
  • storage
  • docker hosted dokku

---

Note: We've added the official storage plugin in 0.5.0

[louisbl]

• Version of dokku you use: 0.4.14
  

• Non-core plugins you use:
  

  • dokku-docker-auto-volumes
  • dokku-slack
  • dokku-logspout
  • dokku-deploy-script (custom pre-deploy script for Dockerfile)

• Company Name: Oz Conseil
  

• Size of team using dokku: 7
  

• Primary role of the dokku maintainers at your company: dev/ops
  

• Primary use of dokku: dev/staging
  

• Where you host dokku: internal (with proxmox) / bare-metal at online.net
  

• How you deploy dokku: ansible/deb package
  

• Number of servers hosting dokku: 2
  

• Best current feature you love about dokku:
  

  • zero-downtime deploy
  • Dockerfile support
  • plugins system

• The worst thing ever about dokku:
  

  • restart policy/ps:restore failing with linked container

• Something you'd love to see in the near future for dokku:
  

  • docker-compose support
  • simpler rollback (including db)
  • storage

---

Note: The planned docker-compose support was scrapped in favor of supporting Procfile commands in dockerfile-deploys, which is what most users actually wanted.
Note: We've added the official storage plugin in 0.5.0

[christiangenco]

• Version of dokku you use: 0.4.14
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • none
• Company Name: DBinbox
• Size of team using dokku: me
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): ops/dev/founder
• Primary use of dokku (staging env, local test, production): production, staging
• Where you host dokku (AWS/Linode/Digitalocean): Digitalocean and Chunkhost proxied by Route53 DNS Failover for 99.999999999999999999% uptime.
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): sudo DOKKU_TAG=v0.4.14 bash bootstrap.sh and git push dokku master - moving to jenkins
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • it's the simplest (doesn't try a half-baked multi host deployment), most modular, most stable, and best supported of the Heroku clones (see flynn, deis et al.).
• The worst thing ever about dokku:
  • my Sidekiq workers keep dying and I don't know how to automatically restart them
  • chown takes a super long time to redeploy when apps have been running for a while
• Something you'd love to see in the near future for dokku:
  • [RFC] Revisit docker restart policy #1734: revisit docker restart policy
  • dokku ps:restore fails due to CHECKS file #1943: ps:restore fails due to checks
  • dokku --help is unwieldy, collapse help into commands (topics) similar to heroku and docker #1688: help is unwieldy
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • ketogenic coconut fat bombs

---

Note: We've added better help output in 0.5.0.
Note: We've fixed failing ps:restore runs in a newer herokuish release (0.3.9).

[viktor-evdokimov]

• Version of dokku you use: 0.5.1
• Non-core plugins you use:
  • redis
  • elasticsearch
• Company Name: Sylogent
• Size of team using dokku: 3
• Primary role of the dokku maintainers at your company: devops
• Primary use of dokku: test, stage, prod
• Where you host dokku: rackspace
• How you deploy dokku: manual for now
• Number of servers hosting dock: 2
• Best current feature you love about dokku:
  • simplicity to add apps
  • map domains
  • push to deploy
• The worst thing ever about dokku:
  • not sure yet
• Something you'd love to see in the near future for dokku:
  • web dashboard
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • pineapple-pomegranate, also pineapple-pomegranate fresh is a killer

[dudeofawesome]

• Version of dokku you use: 0.5.1
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • None
• Company Name: Edyza
• Size of team using dokku: 3
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): cofounder
• Primary use of dokku (staging env, local test, production): production
• Where you host dokku (AWS/Linode/Digitalocean): DigitalOcean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): DO Droplet picker
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • Currently the ease of deployment, but I haven't used much else about it.
• The worst thing ever about dokku:
  • Difficulty of hosting non-HTTP endpoints (again, still pretty new to Dokku, I'll be looking in to this more soon)
• Something you'd love to see in the near future for dokku:
  • A web dashboard
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • Cookies and creme

---

Note: We've made proxy handling more flexible (including support for disabling it and container checks entirely) in 0.5.0.

[crisward]

• Version of dokku you use: 0.2.? - 0.4.13 (older one being retired next week)
• Non-core plugins you use
  • dokku-apt
  • mariadb
  • redis
  • lets encrypt
  • elasticsearch
• Company Name: www.duodesign.co.uk
• Size of team using dokku: 3 devs
• Primary role of the dokku maintainers at your company: web devs
• Primary use of dokku (staging env, local test, production): all
• Where you host dokku (AWS/Linode/Digitalocean): linode / digital ocean / dedicated servers (UK2)
• How you deploy dokku: use internal tool
• Number of servers hosting dokku: 1 dedicated, 5 vms, soon to be 8-10 vms
• Best current feature you love about dokku:
  • git push workflow
  • usual advantages of docker
  • ability to use lots of language with screwing up host system
• The worst thing ever about dokku:
  • buildpack documentation can sometimes be sketchy
  • npm cache invalidation (this be more to do with heroku buildpacks than dokku)
  • builds can be slow
• Something you'd love to see in the near future for dokku:
  • much quicker deploys.
• If not lactose intolerant, what your favorite milkshake is:
  • beer, hold the milk.

---

Note: We can't really do much about slow deploys, as it mostly has to do with installing dependencies or whatever your Dockerfile does. Node is the worst offender in this arena.

[josegonzalez]

@crisward @Subtletree please get in touch with me on IRC/Slack (I'm savant on both).

[lord2800]

• Version of dokku you use: 0.5.3
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • elasticsearch
  • letsencrypt
  • mariadb
  • redis
  • rev
  • graphite
  • maintenance
• Company Name: Just me.
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Everything. There's just me.
• Primary use of dokku (staging env, local test, production): "Production" (really just my own personal website and random side projects) on digital ocean, and my local server which acts as a "production" environment for my homelab
• Where you host dokku (AWS/Linode/Digitalocean): Local server, Digital Ocean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Droplet picker and bootstrap script
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • Everything. Seriously, Dokku is amazing.
• The worst thing ever about dokku:
  • Development moves fast enough that I end up falling behind.
• Something you'd love to see in the near future for dokku:
  • Clearer documentation on plugins that provide services (I'd love to add support for Consul).
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • Strawberry

---

Note: We've been enhancing usage documentation for all the official storage plugins, but I recommend filing issues wherever possible about stuff that is missing/unclear.

[shingara]

• Version of dokku you use: 0.4.14
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • dokku-logspout
• Company Name: Teezily
• Size of team using dokku: 5
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): dev/ops
• Primary use of dokku (staging env, local test, production): staging env and production
• Where you host dokku (AWS/Linode/Digitalocean): AWS Ec2
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Ansible
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • dockerfile support
  • easy setup of app
• The worst thing ever about dokku:
  • difficulties to configure the nginx configuration
• Something you'd love to see in the near future for dokku:
  • Manage of multi-host or top on docker scheduling system ( k8s or docker swarm )

---

Note: We've since updated the nginx-vhosts support in 0.5.0 to be more rigorously tested and flexible in it's handling of various use cases.

[jwigley]

• Version of dokku you use: 0.4.9
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • dokku-logging-supervisord
• Size of team using dokku: 1
• Primary use of dokku (staging env, local test, production): production
• Where you host dokku (AWS/Linode/Digitalocean): Digitalocean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): DO Droplet picker
• Number of servers hosting dokku: 1
• Best current feature you love about dokku:
  • ease of deployment
• The worst thing ever about dokku:
  • debugging when deploys go wrong
• Something you'd love to see in the near future for dokku:
  • looking forward to the restart policy coming back ( 1734 )
  • web interface/dash
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • chocolate

[clay-to-n]

• Version of dokku you use: 0.5.2
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • letsencrypt (amazing)
• Company Name: Stasis Labs
• Size of team using dokku: 1 or 2
• Primary use of dokku (staging env, local test, production):
  • staging, production
• Where you host dokku (AWS/Linode/Digitalocean): Digitalocean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): DO Droplet picker
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • Can deploy a new server w/ working domain & TLS in a few minutes
• The worst thing ever about dokku:
  • Most of my time has been spent dealing with nginx.conf files in Dokku v0.3. After upgrading and finding the letsencrypt plugin, I don't touch them anymore.

[nickcharlton]

• Version of dokku you use: 0.4.14
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • postgresql
  • redis
  • letsencrypt
• Company Name: It's just for personal projects.
• Size of team using dokku: 1 (Me)
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Developer
• Primary use of dokku (staging env, local test, production): Production for personal projects.
• Where you host dokku (AWS/Linode/Digitalocean): Digital Ocean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Chef
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • App deployment and ease of use of Docker directly.
• The worst thing ever about dokku:
  • Not being 1.0 yet.
• Something you'd love to see in the near future for dokku:
  • some sort of REST API/HTTP interface (something I'm working on).

[nicksergeant]

• Version of dokku you use: 0.4.14
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • letsencrypt (amazing)
• Company Name: Just myself
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): developer
• Primary use of dokku (staging env, local test, production): production
• Where you host dokku (AWS/Linode/Digitalocean): Linode
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Salt Stack
• Number of servers hosting dokku: 1
• Best current feature you love about dokku:
  • one-command deploy
• The worst thing ever about dokku:
  • upgrading?
• Something you'd love to see in the near future for dokku:
  • baked-in support for letsencrypt?
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • chocolate

[christiangenco]

@nickcharlton Ooo yeah, baked in letsencrypt would be nice, especially with the new forced SSL.

[nicksergeant]

@christiangenco well with the letsencrypt plugin it works perfectly and amazingly with forced SSL. I guess my only suggestion was baking in letsencrypt instead of needing to install that plugin :)

[roybrey]

• Version of dokku you use: 0.4.14
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • none yet
• Company Name: Shake
• Size of team using dokku: 2
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): dev/cofounder
• Primary use of dokku (staging env, local test, production): staging - productoin
• Where you host dokku (AWS/Linode/Digitalocean): Softlayer by IBM
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): manual for now
• Number of servers hosting dokku: 2
• Best current feature you love about dokku:
  • one line deploy
• The worst thing ever about dokku:
  • build slowness (happens rarely)
• Something you'd love to see in the near future for dokku:
  • better upgrading flow
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
  • dark chocolate

[DavidLemayian]

• Version of dokku you use: v0.19.11
• Non-core plugins you use (including internally developed ones, with their purposes if possible): letsencrypt, redis, postgresql, redirect
• Company Name: Code for Africa
• Size of team using dokku: 4
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Developers
• Primary use of dokku (staging env, local test, production): Staging and production
• Where you host dokku (AWS/Linode/Digitalocean): AWS
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): AMIs
• Number of servers hosting dokku: ~10
• Best current feature you love about dokku: git push dokku and dokku-update
• The worst thing ever about dokku (please be specific, and file issues if necessary!): None that I can think of.
• Something you'd love to see in the near future for dokku: None that I can think of.
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Chocolate chip.

[Cellane]

• Version of dokku you use: 0.19.11
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • elasticsearch
  • hsts
  • http-auth
  • letsencrypt
  • mariadb
  • memcached
  • mysql
  • nginx-max-upload-size
  • redirect
  • redis
• Company Name: 株式会社モンスター・ラボ, but the server described above & below is my personal server
• Size of team using dokku: 1
• Primary use of dokku (staging env, local test, production): personal server, primarily serving my personal website, Matomo analytics, DMARC reporter, Seafile file server, ONLYOFFICE document server and a Portainer instance; besides Dokku-managed containers, the server also runs a personal mail server
• Where you host dokku (AWS/Linode/Digitalocean): Hetzner
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): manually
• Number of servers hosting dokku: 1
• Best current feature you love about dokku: convenience, stability, container & service linking, Let’s Encrypt integration
• Something you'd love to see in the near future for dokku: HSTS integration, more development in the multi-server direction, Caddy or Traefic support

---

Maintainer responses:

• HSTS: As of 0.20.0, we have HSTS enabled by default.
• Multi-server: We have kubernetes and nomad plugins in development, and are working on high-availability for configuration. See the 0.20.0 release blog post for more info.
• Caddy/Traefik: I previously prototyped a Caddy plugin when we were working on the proxy system, though it was never opensourced. The problem is that generally you want the proxy layer to own the entire system, and there isn't currently a way to set a global default. Note that there is an alternative with the dokku-haproxy plugin.

[nahtnam]

• Version of dokku you use: 0.19.11
• Non-core plugins you use: Postgres, Redis
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company: Me
• Primary use of dokku: Production. I have one server running all of my front-ends (on VPSDime, custom install) with 6gb of ram and I have one firewalled DO droplet which only contains databases. Additionally, I added a DO volume and manually move the data folders onto there and linked them. That way I can scale the drive size without changing the CPU/RAM. I have a script, let me know if you are interested in that.
• Where you host dokku: DO
• How you deploy dokku: DO Droplet Picker
• Number of servers hosting dokku: 2
• Best current feature you love about dokku: Dead simple to use, reliable. My favorite is how easy it is to create any kind of database with it. Also letsencrypt is great!
• The worst thing ever about dokku: Kind of slow, commands are still a bit confusing
• Something you'd love to see in the near future for dokku: N/A

[jarthod]

• Version of dokku you use: 0.20.2
• Non-core plugins you use: letsencrypt (very handy!), memcached, mongo, postgres
• Size of team using dokku: Me ☺
• Primary use of dokku: production for very small sites, 5 sites on a $5 DO droplet that I'll scale up if needed ☺
• Where you host dokku (AWS/Linode/Digitalocean): DigitalOcean
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): DO Droplet picker
• **Number of servers hosting dokku: 1
• **Best current feature you love about dokku: The wide compatibility and robustness provided by heroku buildpacks.
• The worst thing ever about dokku (please be specific, and file issues if necessary!): sometimes a bit rough around the edges, e.g: no error message when downloading buildpack (asked on Slack), documentation not always up to date (e.g: Add documentation for --memory option dokku-memcached#46). But nothing really unexpected from a non-comercial project, it's still great ;)
• Something you'd love to see in the near future for dokku: A nice web UI 🎨
  Or for something smaller: commands listing ressources could be a bit more verbose, for example it would be great if apps:list would show links with services (like a tree), current status, number of processes maybe, etc. dokku ps doesn't show processes but the help, overall consistency and discoverability could be a bit improved here IMO. It's not easy to see the global status of the system (including memory used, cpu, etc..)

---

For those of you wanting to contribute monetarily to Dokku's development, you can do so on OpenCollective here. This will allow the core devs to spend more time writing features and improving the overall Dokku experience. Any and all amounts help :)

Thanks a lot! started a pledge on Patreon 👍

---

Maintainer responses:

• Error messages in buildpack downloading: Seems like the buildpack might have been specified incorrectly, and we're investigating.
• Docs out of date: The datastore plugin readme docs have been changed such that we now autogenerate them from the code (and fail CI if they are out of date!). This will likely make its way across all community plugins going forward. The core docs should be quite good as is, though if someone sees anything out of date, please file an issue.
• Web UI: This will likely not be a core project for a variety of reasons (notably time), but an official dokku-api is being worked on (something a bit more polished than dokku/dokku-api). Hopefully this will enable someone more enterprising to create such a web ui.
• Verbose listing: the :list commands are meant to be quick. If you need something more verbose, run the :report command for the plugin you are interested in. You can also call the global report command with an APP argument to see everything about an app. We purposely don't include extra metadata for better compatibility with Heroku output, but also because it is a lot of data, it's slower to query for, and there are no good answers as to what should be included.
• System resource utilization: This is probably better done with a tool such as Grafana and MetrickTank, or even just docker stats. We have a dokku-graphite plugin that exposes Grafana/Graphite, and maybe this is something that can be developed further.

[alexpdp7]

Version of dokku you use:

0.20.4

Non-core plugins you use (including internally developed ones, with their purposes if possible):

The postgres one, although I should migrate away from it.

Company Name:
Size of team using dokku:
Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):

I use dokku for personal use.

Primary use of dokku (staging env, local test, production):

It's production for a couple of small webapps me and acquaintances have developed

Where you host dokku (AWS/Linode/Digitalocean):

VM running on a ProxMox instance on a dedicated server on Hetzner

How you deploy dokku (AMIs, DO Droplet picker, Opsworks):

Puppet

Number of servers hosting dokku:

1

Best current feature you love about dokku:

Using buildpacks and working as a git remote

The worst thing ever about dokku (please be specific, and file issues if necessary!):

My reason for stumbling into this survey was coming to see if Dokku supported Ubuntu 20.04/CentOS 8, as I'm running it on Ubuntu 16.04 and I want to upgrade; CentOS 7 and Ubuntu 18.04 are not ideal.

Something you'd love to see in the near future for dokku:

Faster builds, but this might not a Dokku issue.

* If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):

I think I love them all.

[iamgoodbytes]

• Version of dokku you use: 0.20.4 on Centos 7 (hoping for 8 to be at thing in the future)

• Non-core plugins you use (including internally developed ones, with their purposes if possible): Letsencrypt (will add mongodb soon as well)

• Company Name: GoodBytes / Thomas More University College (Belgium)

• Size of team using dokku: 2 (myself and one student)

• Primary role of the dokku maintainers at your company dev

• Primary use of dokku (staging env, local test, production): dokku allows me to easily deploy and host smaller nodejs apps that me and my students have developed and want to use in school (e.g. a Dribbble-like platform, virtual currency app in our school, ...)

• Where you host dokku (AWS/Linode/Digitalocean): Linode

• Number of servers hosting dokku: 1

• Best current feature you love about dokku: Deployment via git remotes (just add ssh-keys and deploy!)

• The worst thing ever about dokku (please be specific, and file issues if necessary!): This is more related to myself but I spent quite some time before realizing that the web setup didn't exist on CentOS ;)

• Something you'd love to see in the near future for dokku: Continued support for CentOS

Seriously, dokku made me so happy this week because I've tried various ways to move away from heroku in the past and that always bit me in the ***. I'm currently migrating all my nodejs apps over to dokku.

PS: is anyone else always typing dokky instead of dokku in their terminals?

[bayukp]

Version of dokku you use:

0.20.4

Non-core plugins you use (including internally developed ones, with their purposes if possible):

• Letsencrypt
• Mongo
• Redis
• Mysql (for wordpress)

Company Name:

https://paola.id/

Size of team using dokku:

6 (But it's only me operate dokku)

Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):

cofounder,dev,ops

Primary use of dokku (staging env, local test, production):

SIT & Production

Where you host dokku (AWS/Linode/Digitalocean):

Digitalocean

How you deploy dokku (AMIs, DO Droplet picker, Opsworks):

Using script provided on dokku homepage

Number of servers hosting dokku:

1

Best current feature you love about dokku:

• Easy to understand if you came from Heroku
• Push to deploy
• Easy linking plugin
• Easy maintenance

The worst thing ever about dokku (please be specific, and file issues if necessary!):

• Missing web dashboard (Can we have this plz?? This is important for production monitoring)

Something you'd love to see in the near future for dokku:

• Web dashboard!!!! I almost choose Flynn because of this. Fortunately, Flynn project seems dormant make me come back to dokku

---

Question:
Lot's of official plugin still in BETA, is dokku production ready?

Answer:
@iamgoodbytes Yes I always type dokky, even in this post

---

From maintainer: Yeah, the plugins and dokku are production ready. While it's not at a 1.0 - there may be a few breaking API changes, and I want to stabilize a few more features/fix bugs before releasing a 1.0 - it's quite usable today for both single (docker-local) and multi-server (kubernetes, soon nomad) workloads.

[hugopeixoto]

Version of dokku you use:
0.21.1

Non-core plugins you use (including internally developed ones, with their purposes if possible):
letsencrypt and postgresql

Company Name:
No company, I host personal apps and am working on hosting some for local NGOs

Size of team using dokku:
Just me. I'm planning on giving deploy access to some other folks though

Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):

Primary use of dokku (staging env, local test, production):
production

Where you host dokku (AWS/Linode/Digitalocean):
ptisp.pt

How you deploy dokku (AMIs, DO Droplet picker, Opsworks):
bootstrap.sh on Debian (so it installs via apt, indirectly)

Number of servers hosting dokku:
1 for now

Best current feature you love about dokku:
Easy to get started

The worst thing ever about dokku (please be specific, and file issues if necessary!):
Still early to tell, but I'd say that the documentation is more oriented to someone familiar to the project rather than novices.

Something you'd love to see in the near future for dokku:
Having dokku on Debian's repository once it becomes a bit more stable.
Feature wise: make it easy to grant push/env for certain apps to some users (or ssh keys, i guess)

If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
I'd rather go with orange or lemon juice

[pawurb]

Version of dokku you use:
0.20.4

Non-core plugins you use (including internally developed ones, with their purposes if possible):
redis for Sidekiq and cache

Company Name:
Abot https://abot.app/

Size of team using dokku:
Just me.

Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):

Primary use of dokku (staging env, local test, production):
production

Where you host dokku (AWS/Linode/Digitalocean):
AWS

How you deploy dokku (AMIs, DO Droplet picker, Opsworks):
bootstrap.sh via Ansible

Number of servers hosting dokku:
1 for now

Best current feature you love about dokku:
I was used Heroku. Switching to Dokku was surprisingly easy with little devops skills. I've wrote a tutorial about it for RoR stack https://pawelurbanek.com/rails-heroku-dokku-migration

The worst thing ever about dokku (please be specific, and file issues if necessary!):
When something goes wrong with deployment it's sometimes easier to setup everything from scratch than resolve it. https://github.com/dokku/buildpack-nginx was randomly crashing for me when restarting the server, I've gave up dokku for my static website and started using barebones Nginx.

Something you'd love to see in the near future for dokku:
Support for more than 1 server
Better ansible documentation (I found https://github.com/dokku/ansible-dokku quite hard to implement, ended up writing my own playbook from scratch)

If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
I'd pour some matcha in in :)

[kidGodzilla]

Version of dokku you use: 0.21.4 / Latest
Company Name: Meeting Room 365 (https://www.meetingroom365.com/)
Size of team using dokku: 3
Primary role of the dokku maintainers at your company: Founder, developers
Primary use of dokku: Staging, Production
Where you host dokku: DigitalOcean, OVH
Number of servers hosting dokku: 5
Best current feature you love about dokku: ease of use
Something you'd love to see in the near future for dokku: git push dokku main ¯\_(ツ)_/¯
If not lactose intolerant, what your favorite milkshake is: Pineapple

---

From maintainer:

• As of 0.22.1, the first pushed branch will be used as the push branch.

[ArmandoAssuncao]

Version of dokku you use: 0.19.3 - 0.22.8
Non-core plugins you use (including internally developed ones, with their purposes if possible):

• storage
• redis
• max-upload-size
• letsencrypt
• dokku-apt
• script to backup envs (not plugin): https://github.com/ArmandoAssuncao/dokku_backup_envs

Size of team using dokku: 10
Primary use of dokku (staging env, local test, production): dev, production
Number of servers hosting dokku: 15
Best current feature you love about dokku: easy to use
The worst thing ever about dokku (please be specific, and file issues if necessary!): unstable, some containers not deleted automaticaly
Something you'd love to see in the near future for dokku: version 1.x
If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): strawberry, obviously

---

From maintainer:

• 0.23.0 will have the ability to set a custom max upload size: Add ability to set client max body size via nginx:set #4318
• 0.22.0 aggressively clears out old containers, though you may need one manual pass to clean up anything untracked.

[andresribeiro]

Version of dokku you use: latest (v0.23.7)
Non-core plugins you use (including internally developed ones, with their purposes if possible): Dokku Postgres
Size of team using dokku: I am alone in this case (1)
Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Full-Stack Programmers
Primary use of dokku (staging env, local test, production): Production
Where you host dokku (AWS/Linode/Digitalocean): Linode
Number of servers hosting dokku: 1
Best current feature you love about dokku: It's simple and easy to use
How can we contact you for feedback (twitter, email, ...): [email protected]
If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Chocolate

[mrailton]

• Version of dokku you use: 0.24.1
• Non-core plugins you use (including internally developed ones, with their purposes if possible): **Letsencrypt & MySQL **
• Company Name: Personal Server
• Primary use of dokku (staging env, local test, production): staging / production
• Where you host dokku (AWS/Linode/Digitalocean): Contabo
• Number of servers hosting dokku: 2
• Best current feature you love about dokku: Ability to run different languages on same server
• Something you'd love to see in the near future for dokku: An official UI
• How can we contact you for feedback (twitter, email, ...): Twitter
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Strawberry

[illgitthat]

• Version of dokku you use: 0.24.3
• Non-core plugins you use (including internally developed ones, with their purposes if possible): letsencrypt
• Company Name: Personal
• Size of team using dokku: 1
• Primary use of dokku (staging env, local test, production): prod deployment
• Where you host dokku (AWS/Linode/Digitalocean): Azure
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Azure provided ARM template/1 click deploy
• Number of servers hosting dokku: 1
• Best current feature you love about dokku: git push to deploy, super simple letsencrypt config
• Something you'd love to see in the near future for dokku: Better documentation (I know that's vague, but getting started was a bit rocky)
• How can we contact you for feedback (twitter, email, ...): github
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Choco

[josegonzalez]

@illgitthat if you could hop onto our slack so we could walk through your doc issues, that would be great. Your github username doesn't have any contact info.

[nicbet]

Version of dokku you use:
0.24.8

Non-core plugins you use (including internally developed ones, with their purposes if possible):
letsencrypt, memcached, redis, postgres

Company Name:
Various

Primary use of dokku (staging env, local test, production):
Dev, Staging, Production

Where you host dokku (AWS/Linode/Digitalocean):
Digitalocean

Number of servers hosting dokku:
6+

Best current feature you love about dokku:
Full dockerized application stacks with easy deployments via git push

Something you'd love to see in the near future for dokku:
Support deploying apps over multiple dokku servers

How can we contact you for feedback (twitter, email, ...):
Github

If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
Tropical Thunder

Anything Else:
**Thanks for making and maintaining dokku!! ❤️ **

[l3d00m]

• Version of dokku you use: most time latest provided by ubuntu
• Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • letsencrypt (a lot)
  • mysql
  • dokku ansible role (not really a plugin though)
• Company Name: none
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): no company. But I'm a dev and don't want to spend 50% of my time on configuring deployments. The combination of ansible+dokku+Github Actions makes it possible to spend very little time on getting a new site online.
• Primary use of dokku (staging env, local test, production): mostly as production host, sometimes as staging as well (dokku clone is helpful for that)
• Where you host dokku (AWS/Linode/Digitalocean): Self host on VPS from Hetzner/OVH (configured with ansible)
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Usually Github Actions
• Number of servers hosting dokku: 2-3
• Best current feature you love about dokku: the little effort you need to deploy an app of any language/framework, which is incredibly helpful. I just have to add a git remote and push, and don't need to commit any additional files to make it work with dokku! Also zero-downtime deployments and dependency caching <3
• The worst thing ever about dokku (please be specific, and file issues if necessary!): Modifying the default nginx templates is a bit unintuitive and requires a bit more effort, especially if you want http->https or (edit: afaik letsencrypt plugin does this automatically, nvm!) www->non-www redirects.
• Something you'd love to see in the near future for dokku: native letsencrypt support
• How can we contact you for feedback (twitter, email, etc. please add contact info to github if that is your choice):
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): oreo and coffee

Thank you for continuing to develop and maintain dokku <3

[Xantios]

Version of dokku you use: Latest
Non-core plugins you use (including internally developed ones, with their purposes if possible): Currently none, thinking about building one to spam my discord server
Primary use of dokku (staging env, local test, production): Indie developer / Hobbyist dev hosting
Where you host dokku (AWS/Linode/Digitalocean): At home
How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Ssh to a VM and run the bootstrap script
Number of servers hosting dokku: 2
Best current feature you love about dokku: Its like Heroku, but without going bankrupt
The worst thing ever about dokku (please be specific, and file issues if necessary!):
Something you'd love to see in the near future for dokku: I would LOVE a web interface
How can we contact you for feedback (twitter, email, etc. please add contact info to github if that is your choice): @xantioss on Twitter
If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Chocolate Milkshake at McDonalds and BurgerKing in NL are 1337h4x0rdrink of choice 👍

[froodi]

1. Version of dokku you use: 0.21.4
2. Non-core plugins you use (including internally developed ones): dokku-postgres, letsencrypt
3. Company Name: BOOSTERS / startup for which we use Dokku is called Froodi
4. Size of team using dokku: 4
5. Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Dev + Founder
6. Primary use of dokku (staging env, local test, production): Staging and Production
7. Where you host dokku (AWS/Linode/Digitalocean): Digitalocean
8. How you deploy dokku (AMIs, DO Droplet picker, Opsworks): DO Droplet
9. Number of servers hosting dokku: 3
10. Best current feature you love about dokku: ease of use in automation of services, and the CLI.
11. The worst thing ever about dokku: sometimes very brief documentation/errors.
    (Update; just found www.dokku.com! 😄👍)
12. Something you'd love to see in the near future for dokku: CA handling (letsencrypt), handling of (staging/production) secrets.
13. If not lactose intolerant, what your favorite milkshake is: Strawberry 🥤, of course. Next to Jolt. (Dûh!)

Thanks for Dokku & keep up the good work!

[nenord]

1. Version of dokku you use: 0.26.6
2. Non-core plugins you use (including internally developed ones): dokku-couchdb
3. Company Name: none, hobby projects
4. Size of team using dokku: 1
5. Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): one ops/dev person
6. Primary use of dokku (staging env, local test, production): staging and production
7. Where you host dokku (AWS/Linode/Digitalocean): Digitalocean
8. How you deploy dokku (AMIs, DO Droplet picker, Opsworks): ‘git push’ from local repo
9. Number of servers hosting dokku: 1
10. Best current feature you love about dokku: ease of deploying application
11. The worst thing ever about dokku: the decision to drop API feature from free version and allowing it on Pro only (It is a serious hindrance for using dokku in interesting projects. I understand it makes business sense, but it prevents open source community from making very creative solutions. For example OpenStack has full API available.)
12. Something you'd love to see in the near future for dokku: 1. make API feature available in free app ; 2. deploying apps over multiple dokku servers

I love dokku, and I appreciate the work you are doing very much. I can be contacted via github account.

---

From maintainer:

• The dokku-api project is still open source. If you'd like to take over maintenance of it, feel free to message me via email.
• We provide ansible modules if you are interested in automation, and there is a community project providing terraform integration.
• While it might be nice to provide the pro api as free to everyone, I've said over the years that I would never do such a thing for free. The amount of money donated to the project would be nowhere near the amount needed to cover my development cost, let alone continue to develop it. I fail to see what interesting projects in the OSS community would benefit from having the api I maintain be free, given that automation projects are continuing on without it.
• You can use the kubernetes or [nomad](https://github.com/dokku/dokku-scheduler-nomad] for multi-server deployments.
• The current github goal to is set for built-in swarm support. Of course if folks want to develop and contribute it to the core on their own time, that would be good as well.

[chrisjsimpson]

Purpose: Dokku made it easier to write a 'minimal continous delivery' repo which may be useful for learners wanting to get into DevOps
Best current feature you love about dokku: Ease of use and use of standard tooling/not overly complex

https://github.com/KarmaComputing/minimalcd

How can we contact you for feedback: twitter

Thank you for the efforts which go into it. Hope the exposure helps find more contributers.

[AndrewKvalheim]

• Version of Dokku you use: 0.27.5
• Non-core plugins you use: letsencrypt
• Organization Name: SeaGL
• Size of team using Dokku: 3
• Primary role of the Dokku maintainers: ops
• Primary use of Dokku: production
• Where you host Dokku: AWS
• How you deploy Dokku: Ansible
• Number of servers hosting Dokku: 1
• Best current feature you love about Dokku: simplicity of use
• The worst thing ever about Dokku: It’s unclear how running containers should receive security updates. I’m surprised to have found little to no mention of the topic in the docs. Ideally Dokku would be opinionated and recommend some strategy.
• Something you'd love to see in the near future for Dokku: ^
• How can we contact you for feedback: first name @ organization

[SaadBazaz]

Lack of a web panel / dashboard is the sole reason why I'm still using CapRover - even though it doesn't even support docker-compose, which is my major task.

Legit, Dokku team is missing out on an entire market. Should be prio'd asap.

---

From maintainer: Purchase Dokku Pro if you absolutely need a UI.

[josegonzalez]

The nice thing about Dokku is that it's open source, and if you don't wish to use the project, you can use anything else. Purchasing a license is effectively sponsoring my time on the project, and if you don't wish to sponsor my time, thats okay too.

I wish you and others luck in whatever other project you wish to use.

[gamedevsam]

• Version of dokku you use: 0.30.7
• Company Name: None, just me
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company: N/A
• Primary use of dokku: Tinkering for now, would like to start a micro SaaS at some point
• Where you host dokku: Hetzner Cloud
• How you deploy dokku: I just installed it manually
• Number of servers hosting dokku: 1
• Best current feature you love about dokku: The ease of setting up & deploying a node based app with a postgres DB attached to it, and debug deployment / build issues locally through docker.
• The worst thing ever about dokku: dokku-pro lacks polish and doesn't handle most functionality offered by the CLI (not a big deal though) and the ability to rollback to a previous build instantly if a bug is found in production
• Something you'd love to see in the near future for dokku: Moar functionality for dokku-pro!
• How can we contact you for feedback (twitter, email, etc. please add contact info to github if that is your choice): Hit me up on Discord: GameDevSam#7734
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Peach?

[arusa]

• Version of dokku you use: 0.30.7
• Non-core plugins you use (including internally developed ones, with their purposes if possible): (I'm not sure what exactly is meant with non-core)
  • dokku-monit
  • postgres
  • http-auth
  • maintenance
  • redirect
  • redis
  • letsencrypt
  • ...
• Company Name: spread emotions GmbH
• Size of team using dokku: 1
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): CEO/cofounder
• Primary use of dokku (staging env, local test, production): production
• Where you host dokku (AWS/Linode/Digitalocean): Hetzner Cloud
• How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Prepare Server with Ansible and manually run 12 commands to install and configure Dokku + plugins + SSH key
• Number of servers hosting dokku: 8
• Best current feature you love about dokku: herokuish deploying, letsencrypt and database management
• The worst thing ever about dokku (please be specific, and file issues if necessary!): Nothing - maybe, that I can't update plugins with apt upgrade - or that I can't see if there are plugin updates available before updating
• Something you'd love to see in the near future for dokku: dokku plugin:report or dokku plugin:available-updates
• How can we contact you for feedback (twitter, email, etc. please add contact info to github if that is your choice): Twitter @der_alex_at
• If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Banana

[rahoulb]

Hi @josegonzalez - firstly thank you so much for Dokku. As a dev, rather than an ops, it's made my life so much easier.

• Version of dokku you use: Latest
• Non-core plugins you use: None - I use nearly all the core ones though
• Company Name: Collabor8Online (day job) && EchoDek (freelance) && Standard Procedure (side project)
• Size of team using dokku: Just me
• Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): CTO && Owner && Owner
• Primary use of dokku: All application servers
• Where you host dokku: @brightbox Cloud (highly recommended UK based hosts), Hetzner
• How you deploy dokku: Originally by hand, now using cloudinit - see below
• Number of servers hosting dokku: possibly 20 in total?
• Best current feature you love about dokku: That I don't have to learn how to install and maintain all those other bits of server software
• The worst thing ever about dokku: Keeping everything in sync - but see below
• Something you'd love to see in the near future for dokku: docker compose support - but see below
• How can we contact you for feedback (twitter, email, etc. please add contact info to github if that is your choice): Email: [email protected], Mastodon: @[email protected]
• If not lactose intolerant, what your favorite milkshake is: Chocolate with chocolate ice cream, chocolate sauce and chocolate sprinkles

---

I'm a Ruby on Rails dev and while I can figure out server management, I hate writing shell scripts and all my servers were slightly different to each other as I didn't have a consistent process for them.

Dokku is a life-saver in that regard.

But I was running into problems - I have a number of freelance clients (7 at last count) that I've been moving over to dokku (originally on AWS Elastic Beanstalk but that's actually horrible), when I started with my day job @Collabor8Online I used dokku for managing the Rails servers there. Plus my new side project is about to launch which will also be on dokku.

Collabor8 is slightly unusual - the production servers are very busy, so I set up multiple dokku servers behind a load-balancer, using Github actions to manage the deployments. To prevent cron jobs and other tasks from running more than once, I set server-specific environment variables - then each cron job has to check whether it's allowed to run. We also have a staging setup, and now we're offering big clients their own set of staging and production servers. At current count, we've got 12 managed by dokku and it's starting to become a headache.

Dokku itself is great. But the initial setup part, setting the environment variables, configuring the plugins - each server was done slightly differently. When running multiple servers for the same app (behind a load-balancer), every now and then I would notice that the environment variables had got out of sync. Lots of little annoyances like that - all beyond the remit of dokku itself, but still stuff I had to deal with.

So I've just built Anvil.

It:

• generates a cloudinit file that installs docker and dokku so you can create your server consistently.
• uses a yaml file to store your app configuration (whether on a single host or multiple hosts) that you can store in your repo. This specifies your plugins, some of the nginx config, your environment variables and defines scripts that run after installation, after first deployment and after subsequent deployments. The environment variables and scripts can be specified for the entire app or for specific hosts.
• it also allows you to specify environment variables separately, so you don't need to keep your secrets in your repository.
• performs the initial installation of your app, setting the environment variables and loading plugins, then running your after-installation scripts
• creates your git remotes and handles the initial deployment of your app, running the after-first-deployment scripts so you can configure your plugins and seed the database (or whatever)
• performs subsequent deployments, pushing to each remote in turn, then running your after-deployment scripts

It's still very early on, but I've used it successfully for my Rails apps a few times now.

I'd love to get some feedback on it.

Cheers
Baz