An Open Source, Self-Hosted Heroku
bitmatica.com
An Open Source, Self-Hosted Heroku
1–10 of 123 posts
Re: An Open Source, Self-Hosted Heroku
#2TLDR: We tried getting something similar to Heroku up and running but we ended up going with a paid service that starts at 4299$/month.
Re: An Open Source, Self-Hosted Heroku
#3TLDR: We tried getting something similar to Heroku up and running but we ended up going with a paid service that starts at 4299$/month.
That's for Managed Flynn. We're using the open source version, which is free:
Re: An Open Source, Self-Hosted Heroku
#4TLDR: We tried getting something similar to Heroku up and running but we ended up going with a paid service that starts at 4299$/month.
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.
Re: An Open Source, Self-Hosted Heroku
#5TLDR: We tried getting something similar to Heroku up and running but we ended up going with a paid service that starts at 4299$/month.
That's for Managed Flynn. We're using the open source version, which is free: https://github.com/flynn/flynn
And nothing for the support offered by the flynn team?
I am also curious to find out what is the running cost for maintaining flynn. Is there one dedicated engineer minitoring the infra?
Re: An Open Source, Self-Hosted Heroku
#6I 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 particular, though, the flynn.io team are particularly excellent in terms of support.
Re: An Open Source, Self-Hosted Heroku
#7I 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 containerization tech is starting to feel like keeping up with new JS frameworks/tooling...
Re: An Open Source, Self-Hosted Heroku
#8I 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…
Thanks for using Flynn!
> There are still a couple of rough edges, specifically around upgrading and persistence across power failure
Indeed, we have been finding and fixing bugs in these two areas lately, and things have been improving. Next week's stable release will have a bunch of fixes for issues we found. We also recently added a bunch of new test coverage for backup/restore, which should ensure that future upgrades go smoothly.
As always, if you see any issues please let us know so that we can fix them!
Re: An Open Source, Self-Hosted Heroku
#9Earlier quoted context omitted.
That's for Managed Flynn. We're using the open source version, which is free: https://github.com/flynn/flynn
And nothing for the support offered by the flynn team? I am also curious to find out what is the running cost for maintaining flynn. Is there one dedicated engineer minitoring the infra?
Our experience at Flynn is that there are a few common scenarios:
- Small and side projects run well without supervision.
- Existing ops teams can manage Flynn without much additional effort.
- Medium sized teams that don't want an internal ops team pay us for Managed Flynn where we take over all ops-related responsibilities.
Re: An Open Source, Self-Hosted Heroku
#10Earlier quoted context omitted.
That's for Managed Flynn. We're using the open source version, which is free: https://github.com/flynn/flynn
And nothing for the support offered by the flynn team? I am also curious to find out what is the running cost for maintaining flynn. Is there one dedicated engineer minitoring the infra?
Yep, the Flynn team helped us out via IRC and were fantastic. Especially as we were still working on getting pre-1.0 running, it was great to work with an engineer directly through the bumps. Obviously they do offer paid support as well, which is great for recurring issues and operational assistance.
We do have a dedicated engineer managing / monitoring our infrastructure. It's not a set-it-and-forget-it kind of thing, so if you don't have somebody to manage your infrastructure, the hosted version might be a better choice.
The big cost savings win was for all of our /other/ engineers who now don't need to know anything about ops to get their apps running. Previously with Chef, everybody was responsible for writing recipes and setting up environments, but now we have a standard set of buildpacks that work with our apps, and when we need to transfer an app to a client (as we're a dev agency), we can set it up on Heroku and it should "just work".