progrium

Dokku is sort of a proto-Flynn. It has different, more reachable goals because it's intended for a single host. It solves some of the same problems, just in a non-distributed way. Breaking Dokku down into its components starts providing part of the plan for Flynn.

They may even share code in the end, but Dokku will remain focused on simple, single host deployments. Flynn is about a real, distributed system that could be used in production.

Since Flynn is really just a packaged collection of components (similar to Dokku), Dokku may just end up being a single host version of Flynn someday.

They give a lot away for free. Too much even. Really it's the addons that get expensive.

Some of the components or some of the early validation of the types of components are already open source in the project Dokku.

Docker is in very active development and issues like this get resolved every week. That said, it's not a problem because of the service discovery and routing that would be involved in the Flynn system.

Docker was a big piece of the puzzle. I worked with DotCloud to make Docker happen and we're involved in that community quite heavily. There's still a lot more work to do, otherwise we would not be bothering with a campaign like this.

This HTTP bias has been my problem with the approach of most platform services since the beginning.

Most people don't realize it but they just want to run a process. That's where the computation is defined that you care about. And in many cases, you want to run a long running daemon process. So why are we futzing around with hosts and virtual machines? If all you want is to run managed processes in a cloud (which is what you should want), then OpenStack is unnecessary. You could just write automation around Docker, regardless of whether you're using EC2 or physical servers.

Velociraptor is def a cool project.

I had this argument last night. Ultimately I probably won't care if people say it wrong relative to author intention. Some people will know, others won't. I just want to at least document the intended pronunciation, which is the way the actual word is said in Japanese. Which, btw, means "dock" ... the closest I could get to Docker and just happens to sound like Heroku.

Oh by the way, it's pronounced doh-koo. For the record. :D

Or CloudFoundry.

First, OpenStack is a poor abstraction for what most people want. I don't even think it's worth bothering with if you can help it. Docker is what people should (and will) be building tools around instead of OpenStack. Docker integration in OpenStack is neat and even fun, but to me a distraction.

Autoscaling is interesting because it's only one part of a more complex problem of distributed orchestration. There might not be a good general purpose solution to this for a while. Every organization has different policies and requirements for scheduling resources. Docker was designed to be driven by any sort of automation at that level, but specifically avoids solving that problem.

But there's plenty out there to help you put together this solution for yourself. I'm curious what exactly you're waiting for in a solution.

Yeah, seems party is moving to freenode...

Yes. :)

That and more are some exciting things on my mind.

Yeah, what Solomon said. For the moment, Dokku is focusing on the same sort of stateless apps Heroku supports and considers running databases a separate concern. For now you can run your databases, etc on the same host, in Docker containers, somewhere else, just out of band from Dokku.

But I'd love to hear your thoughts on how Dokku could better support datastores.

I was talking to somebody in the Docker IRC channel that was using some of the same Dokku components to build a more distributed version of Dokku. Not sure if it's released yet.

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.

And if anybody can make it significantly less lines while still being readable, let's see a pull request.

Alex participates in our SuperHappyDevHouse offshoot for kids called Hack the Future, and I also have to mention how passionate Alex is and how well intentioned he had to have been. I was just as impressed by his interaction with the kids, and from what I recall his activity station is usually one of the most popular.

But I definitely share the opinion the project was (and still is) more ambitious than he (or anyone) could pull off on time or on budget.

Cool. That's not far off from what I'm doing, plus I'm already using WebSockets. :)

This was a total surprise! Interesting.

Yes! I forgot all about that. Do you have your current protocol documented? I can document what I was going with and then we can go from there.

I hate that it's using gem for install, too.

How much bigger?

The one day I get bored and check Hacker News, localtunnel is again on the front page. I'm really happy people appreciate it and people keep discovering it. I just want to apologize for neglecting it for so long. People continue to use it despite a few bugs that I've never addressed.

When I get back from vacation, I'm going to focus on releasing v2, which has been in the works for a while. It will continue to be a free service supported by me and hopefully someday the community. Twilio is mentioned, but only because I worked for them recently. Their designer also threw together the website design.

I also want to point out that with version 2 coming out, I'd love input on how to cultivate more community involvement and contributions. I want localtunnel to live for as long as people want to use it, but I will probably move on from it much sooner.

Anyway, thanks again!

Yes! I don't understand why this hasn't happened in Ruby yet either. It seems like one of the ideal next places for it to blow up. A coworker is building up to it, but he's yak shaving by implementing good libuv bindings first. :\

Keep in mind STOMP is an implementation detail in getting ZeroMQ-like sockets in the browser.

Mongrel2 uses ZeroMQ to handle HTTP. Not really the same thing at all.

I updated it to be slightly more useful.

Twilio is just a nice place I work that happens to like what I made.

yep, i never expected this much usage. this will be taken care of.