If anyone is aware of a Docker project being worked on like that. I'd be very interested in seeing it as well.
For example, there is an Openstack integration [1], Hipache and Nginx integration for load balancing [2] [3], and I know several people are exploring integration with Apache Mesos and Zookeeper. There's also a Velociraptor/Docker integration [4].
Lastly, I've seen a lot of ops teams plug docker into their own deployment tools, but those are generally not open-source.
Feel free to drop by the IRC channel (#docker@freenode) to chat some more!
[1] http://github.com/dotcloud/openstack-docker [2] http://index.docker.io/u/samalba/hipache [3] http://github.com/dotcloud/hipache [4] https://bitbucket.org/yougov/velociraptor
Velociraptor does use LXC containers though, and provide the same kind of buildpack support as Dokku, plus a nice dashboard with streaming updates on your processes and some help for managing all the config for your instances (if 2 apps use the same database, you only have to record its URL in one place).
We're running dozens of apps and hundreds of instances on Velociraptor at YouGov, but it still has plenty of rough edges.
The one thing I haven't seen any real solution for is the scaling/autoscaling portion of the equation. I think if that can be solved for, the rest would just be window-dressing on top of the Docker core.
Part of the goal of Dokku is to define some components that would work just as well in a distributed fashion if the components were distributed. By deferring that complexity, I can focus on making something simple and modular that should be easier to do as a distributed system later.
My involvement in Docker in the early stages was with this same thought in mind. Docker was designed to be a component to build things like a PaaS, as well as many other things. Much like the other components of Dokku. The end result is a loosely defined "toolkit" that you can build your own variation of a PaaS with whatever requirements you might have.
Sounds interesting to be sure though! I'll keep an eye on your site.
I currently use Cloudify, but have had some... issues and they use a Java agent which is pretty memory heavy, so I'm working on alternatives. Cloud Foundry is about the only other viable option I've found so far.
Do I just set that stuff up like normal on my box or should I be integrating that with Docker?
Very cool project, would love to get this working and used for internal projects.
But I'd love to hear your thoughts on how Dokku could better support datastores.
(fwiw my first thought was http://www.youtube.com/watch?v=yVdtQfqS9_U )
https://github.com/progrium/dokku/issues/13
Also, be welcome to drop by at #dokku @freenode.
Today however it took 30 seconds so I'm not sure whether it has been updated but a great improvement :-) The only thing I can't wrap my head around in the README is the 'deploy an app' section.
It says to cd into node-js-sample. Where does that folder come from? I created a bare repo called 'node-js-sample' in /home/git and I tried pushing to that but I get this error:
/usr/local/bin/gitreceive: line 54: /home/git/node-js-test/hooks/pre-receive: Permission denied
I looked and that hook doesn't exist (that'd be why! Haha) What's the proper way of creating an app ready to be deployed on the server?
