This looks very nice and seems like a great idea, however I was surprised to see "TODO: Unit tests" in the README, so I peeked around in the source files, and effectively it seems there are no unit tests at all in the repo.
I'm not a TDD test-first evangelist, but 3+ months worth of coding with no test?
I agree with what you say but sometimes when you're bootstrapping an idea, TDD/BDD can get on your way, slowing down things.
I think the author created some prototype, released it and now is checking if it gets the community support.
I was also checking the source code and the front end is done using AngularJS and the project's structure is not that nice. Again, I think this is because of the prototyping stuff.
I'm not an AngularJS wizard but I totally <3 Angular and also I'm totally in for pushing this project forward.
Why don't you start by creating an issue on Github for discussing what's the best solution for reorganising the code?
Keeping track of a project roadmap on HN threads is kinda complicated.
This looks really awesome, but there are enough new concepts floating around that I was hoping to check if I was putting the pieces correctly together.
So, to use this I would
1. Setup a new VM (on Digital Ocean or wherever).
2. Install Docker on the VM
3. Install DockerUI
4. Open firewall ports to let them communicate? And it uses the underlying Unix user permissions?
It should work fine for starting and stopping containers provisioned under Dokku. I played with this UI a few weeks ago and it seemed like a very promising front end. I'm keeping an eye out on Shipyard as well: https://github.com/ehazlett/shipyard
Little to no dependencies - I really want to keep this project a pure html/js app. I know this will have to change so that I can introduce authentication and authorization along with managing multiple docker endpoints.
I'm not a TDD test-first evangelist, but 3+ months worth of coding with no test?