51–60 of 155 posts
I 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.
And this is why you shouldn't open source the core part of your business (looking at you DotCloud). Sure, Docker is good for the community. But it's also a key competitive advantage for DotCloud. By giving away that advantage, they create opportunities for viable competitors.
Hi, I'm the founder of dotCloud and author of Docker. Projects like Flynn are the reason we opened Docker in the first place. They are a good thing for the docker ecosystem, and they are definitely good for dotCloud. The dirty little secret of PaaS is that there is not, and will never be a single PaaS that fits everyone's needs. With docker we offer a foundation for many PaaSes to engage in a healthy competition whil…
What 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.
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.
Earlier quoted context omitted.
The 'cluster' is a group of nodes running the Docker + Flynn software. It can be anything from a single server to a fleet of EC2 instances to a rack of servers. It would be easy to make a tool that spawns instances running Flynn on your choice of public/private cloud.
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…
Don't see Linode listed there, but between that or Jclouds (http://jclouds.incubator.apache.org/documentation/reference/...) you have like a billion cloud API's available to you. I imagine teaming one/both would make Flynn a very interesting alternative to Cloud Foundry/etc.
And this is why you shouldn't open source the core part of your business (looking at you DotCloud). Sure, Docker is good for the community. But it's also a key competitive advantage for DotCloud. By giving away that advantage, they create opportunities for viable competitors.
Hi, I'm the founder of dotCloud and author of Docker. Projects like Flynn are the reason we opened Docker in the first place. They are a good thing for the docker ecosystem, and they are definitely good for dotCloud. The dirty little secret of PaaS is that there is not, and will never be a single PaaS that fits everyone's needs. With docker we offer a foundation for many PaaSes to engage in a healthy competition whil…
Much respect for DotCloud's success thusfar btw.
Earlier quoted context omitted.
Hi, I'm the founder of dotCloud and author of Docker. Projects like Flynn are the reason we opened Docker in the first place. They are a good thing for the docker ecosystem, and they are definitely good for dotCloud. The dirty little secret of PaaS is that there is not, and will never be a single PaaS that fits everyone's needs. With docker we offer a foundation for many PaaSes to engage in a healthy competition whil…
Are you not concerned that once Flynn gets good enough, lots of companies will take a little time to get Flynn set up on VPSes or dedicated servers, rather than pay the high premium for dotCloud?
And this is why you shouldn't open source the core part of your business (looking at you DotCloud). Sure, Docker is good for the community. But it's also a key competitive advantage for DotCloud. By giving away that advantage, they create opportunities for viable competitors.
Hi, I'm the founder of dotCloud and author of Docker. Projects like Flynn are the reason we opened Docker in the first place. They are a good thing for the docker ecosystem, and they are definitely good for dotCloud. The dirty little secret of PaaS is that there is not, and will never be a single PaaS that fits everyone's needs. With docker we offer a foundation for many PaaSes to engage in a healthy competition whil…
I 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.
That way, you get a nice out-of-box experience (push your code, something magic happens), and when you need more control over your build and dependencies, you can add a Dockerfile.
I'm hoping this is what Flynn will do :)
I wonder if there is anyone here who works on CloudFoundry or OpenShift and could comment on this, or comment on the proposed capabilities of Flynn (https://github.com/flynn/flynn-spec) compared to the capabilities of their systems.
I was trying to built something similar, already had a proof of concept ready built on top of components from Dokku. I can't wait to follow this project - I might even pull myself together and learn go!
So am I. What's your project?
Lots of uncomitted changs locally. With this announcement, not sure if its worth continuing down this path.