Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An Open Source, Self-Hosted Heroku

bitmatica.com

Post reply on HN
Print view View original

21–30 of 123 posts

Re: An Open Source, Self-Hosted Heroku

#21

Post by Titanous »

bduerst wrote: post #19
Titanous wrote: post #4

Earlier quoted context omitted.

Hey, I'm a co-founder of Flynn. Flynn is entirely open source and BSD-licensed ( https://github.com/flynn/flynn ). You can run Flynn on any infrastructure without paying us anything. The price you reference is for our Managed Flynn product, where we act as your ops team, operating a Flynn cluster for you and providing hands-on support for your apps and databases in production.

Do you have a comparison chart or something lining Flynn up against Azure/Heroku/Google App Engine somewhere? I know it's probably not as feature-complete as those other PaaS's, but it would be great to get it at a glance.

The space is too complex to do a chart, as a bunch of details are not directly comparable.

Many people who choose Flynn are not directly comparing us to hosted platforms, as they want more control over their infrastructure (where they run it, lock-in avoidance, etc).

As far as individual features go, we are closest to Heroku (and maintain buildpack/runtime compatibility). However there are differences including our support for other databases (MySQL and MongoDB in addition to Postgres and Redis) and many other smaller things like HTTP/2 support.

Re: An Open Source, Self-Hosted Heroku

#22

Post by hashkb »

splitrocket wrote: post #6

I run flynn as a local staging/CI service in our networking closet. It allows us to rapidly try out new apps/services in an environment that approaches production on a couple of machines we had lying around super quickly. There are still a couple of rough edges, specifically around upgrading and persistence across power failures, which is unlikely in a datacenter, but aside from those things, all in all excellent. In…

> In particular, though, the flynn.io team are particularly excellent in terms of support.

Seconding this. I've had many (like 10 or 20) very positive experiences with them, where I went from "OMG WORLD IS ON FIRE" to "oh, sweet, I just delete this row in postgres?"

Re: An Open Source, Self-Hosted Heroku

#23

Post by Shrugs »

zachwill wrote: post #12
mbreedlove wrote: post #7

I just migrated a hobby website to Dokku, which also markets itself as a self-hosted Heroku. I was curious how Flynn compared. Fortunately, there was a blog post giving an overview[1]. I get the impression that Flynn has all the benefits of Dokku, but has the ability to scale to multiple servers. It seems like Flynn is obviously better than Dokku, so I guess I get to do that this weekend. Keeping up with new containe…

I think a lot of us feel your same pain. Has anyone had success with sticking to Dokku for small side projects on DigitalOcean/Linode/etc?

I'd also back dokku for small side projects. I have 4 small slack bots installed on my reserved t2micro instance and I'm pretty happy with it.

Re: An Open Source, Self-Hosted Heroku

#24

Post by stuntkite »

mawalu wrote: post #18

"However, a primary goal of our solution was to automate the process of going from code in a repository to a deployed application in our cluster — much like Heroku. Kubernetes did not appear have any mechanism to support this type of workflow, nor a handful of other features we had hoped to find." Just in case someone is feeling the same, deis[1] is providing exactly this. I did not try their software but I've read a…

I've been using deis in production for ~4 months. It's been great! If I can fit something into a buildpack it's fast to iterate, for more complex concerns you've got the kubernetes backing it up.

Re: An Open Source, Self-Hosted Heroku

#25

Post by ryanSrich »

zachwill wrote: post #12
mbreedlove wrote: post #7

I just migrated a hobby website to Dokku, which also markets itself as a self-hosted Heroku. I was curious how Flynn compared. Fortunately, there was a blog post giving an overview[1]. I get the impression that Flynn has all the benefits of Dokku, but has the ability to scale to multiple servers. It seems like Flynn is obviously better than Dokku, so I guess I get to do that this weekend. Keeping up with new containe…

I think a lot of us feel your same pain. Has anyone had success with sticking to Dokku for small side projects on DigitalOcean/Linode/etc?

I've had success going from heroku to Dokku on DO. Pricing is pretty much the same and Heroku has mature features so I may switch back at some point.

Re: An Open Source, Self-Hosted Heroku

#26

Post by ohstopitu »

I would love to have something like AWS Lambda that can be self hosted on something like this or Flynn.

I know a lot of enterprises that are interested in using serverless arch (the framework serverless[0], not the literal definition of not using servers) but don't want to use AWS or other public cloud providers.

[0]: https://serverless.com

Re: An Open Source, Self-Hosted Heroku

#27

Post by Titanous »

ohstopitu wrote: post #26

I would love to have something like AWS Lambda that can be self hosted on something like this or Flynn. I know a lot of enterprises that are interested in using serverless arch (the framework serverless[0], not the literal definition of not using servers) but don't want to use AWS or other public cloud providers. [0]: https://serverless.com

This would be great!

The open source Parse server (https://github.com/ParsePlatform/parse-server) already works on Flynn, and we can't wait until someone implements an open source system like Lambda.

Re: An Open Source, Self-Hosted Heroku

#28

Post by koolba »

ggrochow wrote: post #11

As someone who's been using flynn in production for a month or two, some things to be aware of. (Devops is not one of my strongpoints, so keep that in mind) You want to use an external blob-store, by default it uses its own postgres to store them. However, it also doesn't do any garbage collection, so we ran out of HD space on our cluster, causing postgres to go into read-only mode. This prevented us from pushing upd…

> You want to use an external blob-store, by default it uses its own postgres to store them. However, it also doesn't do any garbage collection, so we ran out of HD space on our cluster, causing postgres to go into read-only mode. This prevented us from pushing updates / changing any app-config settings ( ENV, Scaling, etc ). Thankfully we were hosting our own DB off-cluster or that too would have been read only.

By garbage collection are you referring to the binary blobs for built slugs?

Re: An Open Source, Self-Hosted Heroku

#30

Post by Titanous »

koolba wrote: post #28
ggrochow wrote: post #11

As someone who's been using flynn in production for a month or two, some things to be aware of. (Devops is not one of my strongpoints, so keep that in mind) You want to use an external blob-store, by default it uses its own postgres to store them. However, it also doesn't do any garbage collection, so we ran out of HD space on our cluster, causing postgres to go into read-only mode. This prevented us from pushing upd…

> You want to use an external blob-store, by default it uses its own postgres to store them. However, it also doesn't do any garbage collection, so we ran out of HD space on our cluster, causing postgres to go into read-only mode. This prevented us from pushing updates / changing any app-config settings ( ENV, Scaling, etc ). Thankfully we were hosting our own DB off-cluster or that too would have been read only. By…

Correct. By default app slugs are stored as large objects in the built-in Postgres cluster, to allow deployment without external dependencies. For production we recommend moving to AWS S3, Google Cloud Storage, or Azure Storage.

Garbage collection of old slugs is supported though it isn't on by default (it will be in the next stable release).

Post reply on HN