Live data from Hacker News

Flynn - Open Source PaaS powered by Docker

flynn.io

111–120 of 155 posts

Re: Flynn - Open Source PaaS powered by Docker

#111

Does anyone know anything like this (a self hosted PaaS) for .NET? I'd love to use docker or something similar for .NET applications.

If your app works with Mono, there's no reason why you can't use Docker/Flynn: https://github.com/friism/heroku-buildpack-mono

That's a good option. Thank you for your insight there.

I can't help but think that this won't really work for many Microsoft shops because the Microsoft CLI is very different from the Mono CLI.

The reason I ask is that there's a number of providers of private PaaS solutions that are willing to install their stuff in your organization for Microsoft stack(HP Matrix, I'm looking at you), but they are full of holes and aren't nearly as robust as what Docker/Dokku/Flynn can offer in terms of plugability and modularity.

Also, free is a pretty good price.

Re: Flynn - Open Source PaaS powered by Docker

#112
post #46

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.

For now, the best way you can help is to try and sell your organization on sponsoring a larger amount. We can help you if they're interested. :)

You are leaving money on the table.

Re: Flynn - Open Source PaaS powered by Docker

#113

My main problem with Docker is that container IP addresses and MACs are changed after every container reboot. This means I can't have a database in one container and a web app in another because I have no way for the web app to discover the address of the database server. Seems like this would be an issue for the host-only (private) network?

This could be solved on AWS with Elastic IP's or OpenStack environments with Floating IP's.

Adding this to Docker would be a nice way to allow new machines to be created but to keep the same IP with automatic switchover.

Re: Flynn - Open Source PaaS powered by Docker

#115
post #113

My main problem with Docker is that container IP addresses and MACs are changed after every container reboot. This means I can't have a database in one container and a web app in another because I have no way for the web app to discover the address of the database server. Seems like this would be an issue for the host-only (private) network?

This could be solved on AWS with Elastic IP's or OpenStack environments with Floating IP's. Adding this to Docker would be a nice way to allow new machines to be created but to keep the same IP with automatic switchover.

There has been some work around integrating docker iwth Openstack floating IPs already. Check out http://github.com/dotcloud/openstack-docker

Re: Flynn - Open Source PaaS powered by Docker

#116

Earlier quoted context omitted.

For now, the best way you can help is to try and sell your organization on sponsoring a larger amount. We can help you if they're interested. :)

You are leaving money on the table.

I don't think the point is to "profit" as much as it is to fund the project. Notice these aren't "customers" but sponsors. Maybe the mindset of "money is being left on the table" isn't quiet the right one for this sort of project ...

Re: Flynn - Open Source PaaS powered by Docker

#117

Earlier quoted context omitted.

For now, the best way you can help is to try and sell your organization on sponsoring a larger amount. We can help you if they're interested. :)

You are leaving money on the table.

Seriously. When I first went to the website and read the description, I was like, "why isn't this already funded? They're only asking for $75K." Now I know why.

Re: Flynn - Open Source PaaS powered by Docker

#118

Earlier quoted context omitted.

You are leaving money on the table.

Seriously. When I first went to the website and read the description, I was like, "why isn't this already funded? They're only asking for $75K." Now I know why.

Thanks--We'll definitely accept individual contributions before the fundraising period ends. We wanted to avoid staff at companies contributing individually instead of bringing institutional support. Flynn's long term success will depend on institutional adoption (not contributions), so forging strong relationships in that area now is important.

We're also considering different options e.g. Gittip vs traditional kickstarter-esque funding options with stickers and t-shirts. Currently there are 13 days on the clock, we'll post again when we're nearing deadline.

We'd be excited to hear any suggestions you have on how to balance individual and organization contributions and participation before then.

Thanks again for your support

Re: Flynn - Open Source PaaS powered by Docker

#119

Earlier quoted context omitted.

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?

Flynn is particularly appealing to companies that need to completely control their own infrastructure. In the same sense that git being open source helps, not hurts github, I think there's limited crossover between the users of Flynn and DotCloud customers.

I think this is a false analogy.

GitHub did not create Git, nor is their code open source.

Re: Flynn - Open Source PaaS powered by Docker

#120
Re: 1500 Minimum, definitely understand the model you're going for, but some of us ARE companies, just really small.

I'd be happy to contribute at a lower level (at least $100, possibly up to $500) as I do see the value in this.

Dokku is more than sufficient for my needs at the moment, but see Flynn as a natural extension to that.

Post reply on HN