I'd love to see a comparison between this and [deliver](https://github.com/gerhard/deliver)
Flynn - Open Source PaaS powered by Docker
41–50 of 155 posts
Re: Flynn - Open Source PaaS powered by Docker
#42Earlier quoted context omitted.
I don't see this in the FAQ: the magic that makes all of this happen (which you're integrating) is technology built by other developers. Why should we be supporting you to do this work rather than the other developers who broke ground and already did a majority of the heavy lifting?
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.
Not to discount your work, but the way I see it: the kernel (e.g. cgroups, namespaces) and the corresponding lxc work dwarfs anything docker brought to the table. This project smells like a campaign to get a product funded.
Re: Flynn - Open Source PaaS powered by Docker
#43What are the advantages/disadvantages compared to Dokku (http://progrium.com/blog/2013/06/19/dokku-the-smallest-paas-...)? It is also based on Docker, super easy to set up on your own server and: Available today.
Re: Flynn - Open Source PaaS powered by Docker
#44Earlier quoted context omitted.
So integrating with VPS providers such as Linode and Digital Ocean will be possible? If so, would this be easy to do for end-users? Never got in to Cloud Foundry because it's overly complex and very limiting. Always went with Heroku, but wished I could have a Heroku-style infrastructure on the above mentioned VPS providers for the benefits of running better hardware, being more affordable, being multi-region, etc, et…
Yes, there's no reason this can't run on VPS providers. Some have APIs for provisioning, so hooking them up for automated deployment is not complex either.
Neat! These two in particular both have an API for provisioning.
Re: Flynn - Open Source PaaS powered by Docker
#45Heroku I'm looking at you, lower your prices.
They give a lot away for free. Too much even. Really it's the addons that get expensive.
Re: Flynn - Open Source PaaS powered by Docker
#46I wanted to contribute but I am a single freelance developer, I don't have the amount of money shown on the sponsorship options. I would be great to have a USD 50 option there.
Re: Flynn - Open Source PaaS powered by Docker
#47Earlier quoted context omitted.
So integrating with VPS providers such as Linode and Digital Ocean will be possible? If so, would this be easy to do for end-users? Never got in to Cloud Foundry because it's overly complex and very limiting. Always went with Heroku, but wished I could have a Heroku-style infrastructure on the above mentioned VPS providers for the benefits of running better hardware, being more affordable, being multi-region, etc, et…
Docker runs on linode and digital ocean ( https://github.com/dotcloud/docker/issues/469 , https://github.com/dotcloud/docker/issues/424 ) by loading a custom kernel. Assuming the requirements for Flynn aren't much more than Docker, the whole stack should run there as well. Easy for end-users is probably a matter of opinion, especially until Flynn releases some code.
Very cool. Thanks for the info!
Re: Flynn - Open Source PaaS powered by Docker
#48I like the fact that Flynn will be written primarily in Go. That should mean very little overhead for this PaaS.
I wonder if using Heroku buildpacks is a good idea, though. Something that can more fully take advantage of Docker layers, and in some cases APT packages for language runtimes, would be better IMO.
Re: Flynn - Open Source PaaS powered by Docker
#49Re: Flynn - Open Source PaaS powered by Docker
#50What are the advantages/disadvantages compared to Dokku ( http://progrium.com/blog/2013/06/19/dokku-the-smallest-paas-... )? It is also based on Docker, super easy to set up on your own server and: Available today.
The Dokku author is one of the guys behind this project.