Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Who uses dokku and for what purposes? #1878

Open
josegonzalez opened this issue Jan 22, 2016 · 68 comments

Comments

Projects
None yet
@josegonzalez
Copy link
Member

commented Jan 22, 2016

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:
  • 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

This comment has been minimized.

Copy link

commented Jan 22, 2016

  • 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

This comment has been minimized.

Copy link
Member

commented Jan 23, 2016

  • 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

This comment has been minimized.

Copy link

commented Jan 23, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Jan 23, 2016

  • 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 :trollface:
@madflow

This comment has been minimized.

Copy link
Contributor

commented Jan 23, 2016

  • 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

This comment has been minimized.

Copy link

commented Jan 24, 2016

  • 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

This comment has been minimized.

Copy link

commented Jan 24, 2016

  • 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

This comment has been minimized.

Copy link
Member

commented Jan 24, 2016

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

This comment has been minimized.

Copy link

commented Jan 30, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Feb 9, 2016

  • 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 #553)
@Subtletree

This comment has been minimized.

Copy link

commented Feb 17, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Feb 19, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Feb 23, 2016

  • 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:

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

@louisbl

This comment has been minimized.

Copy link
Contributor

commented Mar 2, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2016

  • 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:
  • Something you'd love to see in the near future for dokku:
    • #1734: revisit docker restart policy
    • #1943: ps:restore fails due to checks
    • #1688: help is unwieldy
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):

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

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2016

  • 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

This comment has been minimized.

Copy link

commented Mar 28, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Apr 1, 2016

  • 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

This comment has been minimized.

Copy link
Member Author

commented Apr 1, 2016

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

@lord2800

This comment has been minimized.

Copy link

commented Apr 1, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2016

  • 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

This comment has been minimized.

Copy link

commented Apr 12, 2016

  • 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

This comment has been minimized.

Copy link

commented Apr 12, 2016

  • 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

This comment has been minimized.

Copy link

commented Apr 15, 2016

  • 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

This comment has been minimized.

Copy link

commented Apr 18, 2016

  • 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

This comment has been minimized.

Copy link
Contributor

commented Apr 18, 2016

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

@nicksergeant

This comment has been minimized.

Copy link

commented Apr 18, 2016

@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

This comment has been minimized.

Copy link

commented Jul 1, 2016

  • 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
@alexgleason

This comment has been minimized.

Copy link
Contributor

commented Aug 26, 2016

  • Version of dokku you use: the one that comes with the DigitalOcean image
  • Non-core plugins you use: rootplugin and rootconfig which force users to use sudo to view and change plugin/config settings. Also logmem to log memory usage so we can tell when it has run out.
  • Company Name: Direct Action Everywhere, and also a web collective agency I'm currently developing
  • Size of team using dokku: 4
  • Primary role of the dokku maintainers at your company: Developers
  • Primary use of dokku: Production
  • Where you host dokku: DigitalOcean
  • How you deploy dokku: git for custom code, or shell in and use a Docker image for self-hosted services
  • Number of servers hosting dokku: 2
  • Best current feature you love about dokku:
    • Everything
  • The worst thing ever about dokku:
    • New concepts are difficult, but then you wield unlimited power so I can't really complain. The docs could be improved.
  • Something you'd love to see in the near future for dokku:
    • Heroku stops existing and everyone switches to Dokku
  • If not lactose intolerant, what your favorite milkshake is:
    • The dairy industry is incredibly violent and unnecessary. Baby cows are stolen from their mothers at the moment of their birth, immediately killed for veal if they are male, and otherwise are put on a path to lead a life of Hell as a dairy cow. We may dismiss this as "the circle of life" or whatever, but in reality you would not slit a baby cow's throat in exchange for an ice-cream cone unless you are incredibly sadistic. It's time to stop abusing animals and join the animal liberation movement. Otherwise, assuming it's a non-dairy based shake, probably chocolate.
@darklow

This comment has been minimized.

Copy link
Contributor

commented Aug 30, 2016

  • Version of dokku you use: 0.5.6
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • Size of team using dokku: 3
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): developer/cto
  • Primary use of dokku (staging env, local test, production): production
  • Where you host dokku (AWS/Linode/Digitalocean): Hetzner dedicated servers
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): git push dokku with buildpacks, sometimes using Dockerfile and some custom buildpacks.
  • Number of servers hosting dokku: 3 servers with ~10-15 apps on each
  • Best current feature you love about dokku: buildpacks support, ability to run centralised services by plugins (redis, postgresql), full stack paas, ease of deployment.
  • The worst thing ever about dokku:
    • Lack of single config file to define all the envs, domains, plugin configs, links etc.
    • Stability while upgrading. This scares me every time i do dokku upgrade. After one particular update when nginx templates changed to sigil all my 10-15x apps wen't down for quite a while until I fixed every each of them, because nginx template syntax was changed. It would be great to have a deprecation warning for few versions instead of just creating backwards incompatibility.
  • Something you'd love to see in the near future for dokku:
    • Single config file that dokku would read from .git repo with all the env vars, subdomains, links and rest of the settings per plugin. So that I could easily relocate project to another server. Right now I basically need to keep deploy-dokku.txt file for each project to write down all the commands that needed to be run to successfully deploy an app.
    • Some simple UI maybe to overview app settings, volumes. When hosting more apps, scrolling cli and overviewing apps is becoming harder. Something similar to Rancher UI would be awesome.
    • Stacks as a possibility to define more than one container per app (similar to Racher stacks, services and side-kick containers)

We highly recommend that users check the migration guides when they are upgrading minor versions (in the pre-1.0 release). After 1.0, we'll only make BC changes during major releases.
There is the dokku-require plugin for having a more complete application manifest available for all applications, though #2269 is something we've thought about implementing in the core for having more complete initial app deployments.

@srna

This comment has been minimized.

Copy link

commented Sep 2, 2016

  • Version of dokku you use:
    • 0.7.0
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
    • mysql
    • global-cert
    • postgres
  • Company Name: viritech
  • Size of team using dokku: 3
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): devops
  • Primary use of dokku (staging env, local test, production): staging, but planning production
  • Where you host dokku (AWS/Linode/Digitalocean): OVH
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): installed clean ubuntu and ran the dokku installer
  • Number of servers hosting dokku: 1
  • Best current feature you love about dokku:
    • heroku-compatible buildpacks
  • The worst thing ever about dokku:
    • i don't know yet
  • Something you'd love to see in the near future for dokku:
    • web interface
    • acl
@GRardB

This comment has been minimized.

Copy link

commented Sep 17, 2016

  • Version of dokku you use:
    • 0.7.1
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
    • dokku-letsencrypt
    • dokku-psql
    • dokku-redirect
  • Company Name:
    • None!
  • 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):
    • 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:
    • The plugin system is amazing. I was able to set up TLS incredibly fast.
  • The worst thing ever about dokku:
    • I recall having some issues getting domains set up. Unfortunately, I don't remember the exact details 😞
  • Something you'd love to see in the near future for dokku:
    • Feature-wise, it already suits my needs. I think it'd be really cool to have some guides/tutorials on setting up a bunch of different
      stacks. If it wasn't for someone in the Ember.js Slack helped me out a lot at first, I would've been pretty lost, since it seems like
      not a lot of people use Dokku with Ember + Rails.
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
    • Typically peanut butter. Just last night, however, I had a salted caramel milkshake from Honeymee, and that was exceptional.
@nickcharlton

This comment has been minimized.

Copy link

commented Sep 17, 2016

@GRardB: I'm curious to hear what you found difficult with Rails & Ember?

I'm not using Ember, but I am Rails almost exclusively on Dokku. Perhaps we'd be able to both help with some documentation clarification or something!

@kjschulz

This comment has been minimized.

Copy link
Contributor

commented Sep 19, 2016

  • Version of dokku you use:
    • 0.6.5
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
    • dokku-letsencrypt
    • dokku-mongo
  • Company Name(s):
    • ['Ample', 'Ellipsis']
  • 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):
    • 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:
    • 3
  • Best current feature you love about dokku:
    • plugin architecture/community
  • The worst thing ever about dokku:
    • occasionally the documentation is lacking
  • Something you'd love to see in the near future for dokku:
    • A web manager interface
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
    • Peanut Butter
@MikeSchroll

This comment has been minimized.

Copy link
Contributor

commented Sep 25, 2016

  • Version of dokku you use: 0.7.2
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
    • acl 1.0.1 enabled dokku plugin that can be used to restrict push privileges for app to certain users
    • letsencrypt 0.8.0 enabled Automated installation of let's encrypt TLS certificates
    • logging-supervisord 0.1.0 enabled A plugin for dokku that injects supervisord
    • slack 0.4.0 enabled Slack notifier on deploy
    • Most interesting is probably the supervisord one: We have one ruby app that is not web-based; and just processes a log file. So this was the only way I could figure out to run it.
  • Company Name: DNSFilter - OpenDNS alternative
  • Size of team using dokku: 3
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):
    • Founder & CTO
  • Primary use of dokku (staging env, local test, production):
    • dev, stage, test, and prod!
  • Where you host dokku (AWS/Linode/Digitalocean):
    • Softlayer right now - previously DigitalOcean. In the future probably another dedicated server; maybe Packet.net or Enzu through UCXChange
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks):
    • manually on ubuntu.
  • Number of servers hosting dokku: 3
  • Best current feature you love about dokku:
    • plugin integrations for expansion; being able to mount external paths easily.
  • The worst thing ever about dokku:
    • Some brittleness.
  • Something you'd love to see in the near future for dokku:
    • built in ACL support (only allow certain users / SSH keys to deploy to certain apps / create new apps)
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
    • (lactose intolerant - but answer would be Strawberry)
@josegonzalez

This comment has been minimized.

Copy link
Member Author

commented Sep 25, 2016

@MikeSchroll A few questions and comments:

  • You can use the ps:scale command to scale web and non-web processes. No need for any extra process manager plugin.
  • What is brittle about Dokku? Being more exact about issues - and filing them! - is very useful to us. Even if it's something like "oh I didn't know this is how X interacted with Y", as we can improve the UX around Dokku with those sorts of comments.
  • You're familiar with the current ACL plugin. While it would be cool to have in the core/as an official plugin, I think developing it's featureset first is better.
  • You should see if you can switch out milk with coconut milk, might be easier on the stomach :)
@lggwettmann

This comment has been minimized.

Copy link

commented Sep 25, 2016

  • Version of dokku you use: 0.7.2
  • Non-core plugins you use (including internally developed ones, with their purposes if possible): MariaDB
  • Company Name: CIRCLE Dance
  • Size of team using dokku: 1
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): founder
  • Primary use of dokku (staging env, local test, production): for now testing, researching possibility for production use
  • 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: Easyness
  • The worst thing ever about dokku (please be specific, and file issues if necessary!): dokku run was hard to find in the documentation.
  • If not lactose intolerant, what your favorite milkshake is: the funky monkey: peanut butter, banana, chocolate delicious
@WillPlatnick

This comment has been minimized.

Copy link

commented Sep 30, 2016

  • Version of dokku you use:
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
  • Company Name: Life.Church
  • Size of team using dokku: 8 currently, will expand to multiple teams soon
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.): Ops
  • Primary use of dokku (staging env, local test, production): test, production for less important apps
  • Where you host dokku (AWS/Linode/Digitalocean): SoftLayer Bare Metal
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Salt
  • Number of servers hosting dokku: 1 (but with 16 cores, 32 GB RAM, 960 GB SSDs in RAID 1)
  • Best current feature you love about dokku: Easy data stores
  • The worst thing ever about dokku (please be specific, and file issues if necessary!): Lack of ACL system to allow dev's or groups of devs to see only specified apps
  • Something you'd love to see in the near future for dokku: Put rebuild all into the dpkg post installation.
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis) Vanilla
@beberlei

This comment has been minimized.

Copy link

commented Nov 3, 2016

  • Version of dokku you use: 0.4.14
  • Non-core plugins you use (including internally developed ones, with their purposes if possible): CouchDB, LetsEncrypt, MySQL
  • Company Name: private use
  • Size of team using dokku: 1
  • 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): 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: deployment
  • The worst thing ever about dokku (please be specific, and file issues if necessary!): backups, restore
  • Something you'd love to see in the near future for dokku:
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
@CherryDT

This comment has been minimized.

Copy link

commented Nov 11, 2016

Currently it's used mostly for internal projects and tests and quick deploys (such as client demos), but also one small production API.

  • Version of dokku you use: 0.7.2
  • Non-core plugins you use (including internally developed ones, with their purposes if possible): letsencrypt, mongo, secure-apps
  • Company Name: dot labs
  • Size of team using dokku: 4
  • Where you host dokku (AWS/Linode/Digitalocean): AWS
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Vagrant
  • Number of servers hosting dokku: 1

Still getting to know the details...

@dmr

This comment has been minimized.

Copy link

commented Jan 24, 2017

  • Version of dokku you use: 0.3.26, 0.8.0
  • Non-core plugins you use: only core plugins :) nowadays, thanks for building these (letsencrypt, postgresql, elasticsearch, mysql, redis)
  • Company Name: http://netsyno.com
  • Size of team using dokku: 10
  • Primary role of the dokku maintainers at your company: dev, cofounder
  • Primary use of dokku (staging env, local test, production): production
  • Where you host dokku (AWS/Linode/Digitalocean): Own servers
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): manual
  • Number of servers hosting dokku: 3
  • Best current feature you love about dokku: it's just a simple bash script!
  • The worst thing ever about dokku (please be specific, and file issues if necessary!):
    • nobody knows if things work after plugin:update
    • requires a debian based system --> Make the installer check the environment not force it?
    • dokku-acl plugin should be integrated by default and show a different error message because it is hard to debug
  • Something you'd love to see in the near future for dokku:
    • How dokku changed from 0.3 to 0.8 great work with the plugin system!
    • The documentation is hard for new users to read --> Maybe more best practices in the documentation?
    • Not too many breaking updates because dokku is basic infrastructure and upgrading takes time --> call it 1.0.0 and use semantic versioning?
@josegonzalez

This comment has been minimized.

Copy link
Member Author

commented Jan 24, 2017

For those out there who have complaints about dokku - in any way, shape, or form - please contact my on IRC/slack. My nick is savant.

@samfisch3r

This comment has been minimized.

Copy link

commented Jan 26, 2017

  • Version of dokku you use: 0.5.6
  • Non-core plugins you use:
    • Docker Options, to have file storage outside the container. This way one app can upload and resize pictures while the other can use them.
    • Mariadb, storage for piwik.
  • Company Name: dienachbarn.ch
  • Size of team using dokku: 1
  • Primary role of the dokku maintainers at your company: dev
  • Primary use of dokku: production
  • Where you host dokku: Digitalocean
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): to git and then auto deploy to the droplet with Codeship.
  • Number of servers hosting dokku: 1
  • Best current feature you love about dokku: Easy deployment, no server management (auto download of dependencies, nginx conf).
  • The worst thing ever about dokku:
    • I'm afraid of upgrades, last time it broke everything, trying several hours to fix it. Setting up a new droplet with the new version and redeploying everything took less than an hour though.
    • typing a wrong subdomain does not default to the parent domain, but to the first one alphabetically. Setting a fixed order in nginx.conf fixes this, but is not flexible anymore.
  • Something you'd love to see in the near future for dokku: Solid documentation (it's gotten a lot better already)
  • If not lactose intolerant, what your favorite milkshake is: Vanilla
@OmgImAlexis

This comment has been minimized.

Copy link
Contributor

commented Jan 30, 2017

  • Version of dokku you use: 0.8.0
  • Company Name: wvvw.me
  • Size of team using dokku: 1
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):
    All of the above.
  • Primary use of dokku (staging env, local test, production):
    All of the above.
  • Where you host dokku (AWS/Linode/Digitalocean):
    DigitalOcean
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks):
    DO Dokku app
  • Number of servers hosting dokku:
    1
  • Best current feature you love about dokku:
    Auto building on git push
  • The worst thing ever about dokku (please be specific, and file issues if necessary!):
    Let's encrypt not automatically issuing SSL certs.
    The use of Nginx over Caddy as Caddy supports no down time reloads, cors out of the box, auto let's encrypt certs without needing to take the app down, etc.
  • Something you'd love to see in the near future for dokku:
    Caddy or Traefik support instead of Nginx.
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
    Chocolate
@maticrivo

This comment has been minimized.

Copy link

commented Feb 20, 2017

  • Version of dokku you use:
    • 0.8.0
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
    • deployment-keys
    • git-rev
    • hostkeys-plugin
    • redis
  • Company Name:
    • Neura
  • 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):
    • dokku is accessed behind a vpn, it is used for internal dashboards
  • Where you host dokku (AWS/Linode/Digitalocean):
    • AWS
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks):
    • AMIs
  • Number of servers hosting dokku:
    • 1
  • Best current feature you love about dokku:
    • Easy deployment
    • No server management
  • The worst thing ever about dokku (please be specific, and file issues if necessary!):
    • Documentation is hard for first time users
    • Better Let's Encrypt support
    • Afraid to upgrade, stuff usually break
  • Something you'd love to see in the near future for dokku:
    • Web dashboard to manage apps and config settings
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
    • Dulce de leche (Caramel)
@chiedo

This comment has been minimized.

Copy link

commented Mar 7, 2017

  • Version of dokku you use:
    • 0.8.0
  • Non-core plugins you use (including internally developed ones, with their purposes if possible):
    • dokku-mysql
  • Company Name: The Chiedo Companies
  • Size of team using dokku: 7
  • Primary role of the dokku maintainers at your company (ops/dev/cofounder/contractor/etc.):
    • CTO/CEO/Founder
  • 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):
    • gitp2
  • Number of servers hosting dokku:
    • 8
  • Best current feature you love about dokku:
    • Easy deployment.
  • The worst thing ever about dokku (please be specific, and file issues if necessary!):
    • Inconsistent restart policies... I have to continually manually restart my apps.
  • Something you'd love to see in the near future for dokku:
    • A consistent restart policy
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
    • Lactose intolerant. But there are pills for that :) Cookies and Cream
@diogocaetano

This comment has been minimized.

Copy link

commented Mar 27, 2017

Version of dokku you use:
8.0
Non-core plugins you use (including internally developed ones, with their purposes if possible):
redirect 0.4.0 Simple redirects for apps
mysql 1.0.0 dokku mysql service plugin
letsencrypt 0.8.6 Automated installation of let's encrypt TLS certificates
builders-plugin 0.3.3 To run tools and package managers on build/release
Company Name:
Imply Studio
Size of team using dokku:
1
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):
production
Where you host dokku (AWS/Linode/Digitalocean):
digitalocean
Number of servers hosting dokku:
5
Best current feature you love about dokku:
Easy deployment
Something you'd love to see in the near future for dokku:
*easier rollbacks to previous releases (something like #553)
*A web manager interface
If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis):
ovomaltine

@decentral1se

This comment has been minimized.

Copy link
Contributor

commented Feb 14, 2018

Dokku is simply awesome!

Version of dokku you use: 0.11.3 (pre-packed from Digital Ocean Droplet)
Non-core plugins you use: Redis, Postgresql, Letsencrypt
Company Name: https://github.com/giving-a-fuck-about-climate-change
Size of team using dokku: 1 (as of now, aiming for 3+ at least)
Primary role of the dokku maintainers at your company: Full stack people
Primary use of dokku (staging env, local test, production): All environments
Where you host dokku: DigitalOcean
How you deploy dokku: DO Droplet picker
Number of servers hosting dokku: Just one for now.
Best current feature you love about dokku: Everything works! When I need to get inside, there are hooks. For example, NGINX blocks can be added when you need otherwise, you get lovely defaults.
The worst thing ever about dokku: Not enough experience to know.
Something you'd love to see in the near future for dokku: Load balancer baked in. Web UI.

@D1ceWard

This comment has been minimized.

Copy link

commented Mar 22, 2018

  • Version of dokku you use : 0.8.0 (upgrade in progress to 0.11.6)
  • Non-core plugins you use : hostname, letsencrypt, postgres, redis, logspout
  • Company Name : HappyRenting/Avis-Locataire
  • Size of team using dokku : 2
  • Primary role of the dokku maintainers at your company : Devops
  • Primary use of dokku : All environments
  • Where you host dokku : Online.net (french dedicated server provider)
  • Number of servers hosting dokku : 1 (4 apps)
  • Best current feature you love about dokku : Deployment speed/Easy configuration
  • The worst thing ever about dokku : Lack of Arch Linux users/maintainers in community
  • Something you'd love to see in the near future for dokku :
    • Better support for non-debian linux distribution (like detailed installation "to do")
    • Web interface
    • Pipeline for CI
  • If not lactose intolerant, what your favorite milkshake is : Sorry, i'm a hopeless coffee addict :)
@lucasmartins

This comment has been minimized.

Copy link

commented May 2, 2018

  • Version of dokku you use: 0.11.3;
  • Non-core plugins you use (including internally developed ones, with their purposes if possible): memcached, michaelshobbs/dokku-tor, redirect;
  • Company Name: Minerador X
  • Size of team using dokku: 3
  • 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, production.
  • Where you host dokku (AWS/Linode/Digitalocean): GCE
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): manually;
  • Number of servers hosting dokku: 1
  • Best current feature you love about dokku: push to deploy;
  • The worst thing ever about dokku (please be specific, and file issues if necessary!): It's problematic to deploy an app that has no web service, specially if there's a Dockerfile (even when I'm not using a dockerfile based deploy) with an EXPOSE line. It drives me crazy when an app has a problem, and I can't deploy another app because of it. I get an Nginx validation error just because a port is not being used by a service, when dokku expects it should.
  • Something you'd love to see in the near future for dokku: Easier deploy for worker only apps, better isolation between dockerfile based deploys and herokuish based deploys. Today, dokku is not respecting the DOKKU_APP_TYPE set by the user, when theres a Dockerfile with an EXPOSE config. Better isolation between apps, today I cant deploy an app while other app has a problem regarding nginx or port usage;
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Ovomaltine.
@jzumaran

This comment has been minimized.

Copy link

commented Dec 13, 2018

  • Version of dokku you use: 0.11.3
  • Non-core plugins you use (including internally developed ones, with their purposes if possible): memcached, redis, postgres, maintenance
  • Company Name: Citysense
  • Size of team using dokku: 4
  • 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 && Porudction
  • Where you host dokku (AWS/Linode/Digitalocean): AWS
  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): AMIs
  • Number of servers hosting dokku: 6
  • Best current feature you love about dokku: push to deploy
  • The worst thing ever about dokku (please be specific, and file issues if necessary!): I have a ruby on rails app that uses sidekiq to manage workers, everytime I upload a new version of code the workers from the previous version of my app remain alive with the new workers. For example, if I have 4 workers configured in my Procfile, after I upload new code there will be 8 workers alive. After a short while these old workers get deleted and the number goes back to 4.
  • Something you'd love to see in the near future for dokku: Mutli server support (docker swarm)
  • If not lactose intolerant, what your favorite milkshake is (serious question, stop quoting Kelis): Banana Milk Shake
@josegonzalez

This comment has been minimized.

Copy link
Member Author

commented Dec 13, 2018

@jzumaran see this document for more information on how zero downtime deploys work, should help you understand whats going on :)

@jzumaran

This comment has been minimized.

Copy link

commented Dec 13, 2018

@jzumaran see this document for more information on how zero downtime deploys work, should help you understand whats going on :)

I'll check it out, thank you.

@nicolas-brousse

This comment has been minimized.

Copy link

commented Feb 14, 2019

  • Version of dokku you use: 0.14.5

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

    • dokku-postgres
    • dokku-redis
    • dokku-letsencrypt
    • dokku-maintenance
    • dokku-redirect
  • Company Name: Pantographe.studio

  • Size of team using dokku: 1

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

  • Primary use of dokku (staging env, local test, production): staging for now, production soon

  • Where you host dokku (AWS/Linode/Digitalocean): Digitalocean and online.net

  • How you deploy dokku (AMIs, DO Droplet picker, Opsworks): Ansible homemade role

  • Number of servers hosting dokku: 2

  • Best current feature you love about dokku: push to deploy on herokuish way

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

  • Something you'd love to see in the near future for dokku: Mutli server support (docker swarm), and prometheus metrics.

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

@kgrosvenor

This comment has been minimized.

Copy link

commented Feb 14, 2019

Web admin to visualise services / containers would be really nice, I use dokku on a small project with nuxt js, I have a linked mysql image also, I'm really. Impressed with dokku, and can only say that I hope support continues :)

Keep up the great work dokku team, you've created a really great set of tools, and saves us a lot of scripting!

@jxltom

This comment has been minimized.

Copy link

commented Feb 15, 2019

@kgrosvenor Have a look on portainer for web admin

@wmakley

This comment has been minimized.

Copy link

commented Apr 17, 2019

  • Version of dokku you use: 0.15.3
  • Non-core plugins you use (including internally developed ones, with their purposes if possible): PosgreSQL
  • Company Name: tortus.com
  • Size of team using dokku: 2
  • 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 env with entirely containers, no buildpacks
  • 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: Allows us to host multiple staging environments in one place with extremely easy deploys. We wanted a way to easily run a bunch of containers on a web server, and Dokku is kind of the only game in town.
  • The worst thing ever about dokku (please be specific, and file issues if necessary!): Single-user setup is difficult to audit. Could really use a web-based control panel for users less versed in dev-ops to see the status of each app, resource usage, create and delete them, view logs, and map volumes. It would also be easier for the devs.
  • Something you'd love to see in the near future for dokku: Web-based control panel with multiple accounts for auditing of deploys and changes to the server.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.