Recommendations to others considering Dokku:
If you go the Dokku route, keep in mind that your server will have to be administered using mostly Dokku commands... not standard Linux/Unix commands. For example, to check the log files of your application, you don't "cd" to the app directory and check the logs there. Well, you *could*, but you would have a hard time trying to find where your running application is located exactly. Instead, if you want to check your application logs, you use a command like this "Dokku logs myapp". Same thing applies for configuring vhosts, environment variables, etc.
Also, if you don't agree with the "twelve factor app" mindset (http://12factor.net/), you might be disappointed. Review collected by and hosted on G2.com.
What problems is Dokku solving and how is that benefiting you?
With Dokku, I am way more productive in my workflow. This piece of software is perfect to run on a cloud platform such as DigitalOcean. I can isolate each project/client on its own Dokku-ready "droplet" instead of having them all configured on one or more dedicated servers.
I personally use Dokku for Ruby On Rails applications and let me tell you it is a pretty good match. I have written a tutorial on my blog to help people getting start with Rails and Dokku (http://www.rubyfleebie.com/how-to-use-dokku-on-digitalocean-and-deploy-rails-applications-like-a-pro/). Review collected by and hosted on G2.com.