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

81–90 of 123 posts

Re: An Open Source, Self-Hosted Heroku

#81

Post by dchuk »

dawnerd wrote: post #60
zachwill wrote: post #12

Earlier quoted context omitted.

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 was on dokku pretty much from the start but my side projects grew to a point where I needed a little more control so I switched to docker with compose files. Dokku is really nice though - they did a great job making deploying as easy as possible.

Can you share any more details on your deploy process? Do you have a production compose file that you use with images pushed to a registry or something similar?

Re: An Open Source, Self-Hosted Heroku

#82

Post by dawnerd »

dchuk wrote: post #81
dawnerd wrote: post #60

Earlier quoted context omitted.

I was on dokku pretty much from the start but my side projects grew to a point where I needed a little more control so I switched to docker with compose files. Dokku is really nice though - they did a great job making deploying as easy as possible.

Can you share any more details on your deploy process? Do you have a production compose file that you use with images pushed to a registry or something similar?

Nothing fancy, I don't deploy often so I just ssh in, pull down the latest code and do a `docker-compose -d -f docker-compose.prod.yml restart` or something like that.

Re: An Open Source, Self-Hosted Heroku

#83

Post by bacongobbler »

njudah wrote: post #48
mbreedlove wrote: post #42

Earlier quoted context omitted.

Sometimes I have hobby projects that need more than the free tier of Heroku. I get a lot more bang for buck somewhere like Vultr or Digital Ocean compared to Heroku. The standard tier at Heroku is 512MB RAM for $25. Over at Vultr, I can get 2GB RAM for $20. I also get 45GB of SSD, so I don't have to pay for something like Amazon S3 to store uploaded files. If you're building an actual product, I agree with you, pay H…

Since ~mid 2015, the Hobby tier for Heroku has been $7 / month, and since last month, includes SSL.

...which is for hobbies, not businesses.

Re: An Open Source, Self-Hosted Heroku

#84

Post by dabeeeenster »

Titanous wrote: post #67
dabeeeenster wrote: post #64

Earlier quoted context omitted.

Thanks for the reply. Is this something that you have planned in the future? This aspect is a really big part of Heroku/AppEngine/Elastic Beanstalk and saves me a tonne of money each month due to the auto-scaling that we get (we're on AppEngine). Is there a reason projects like Flynn have not tackled it? Or is it just a question of time?

Yeah, it's definitely something we want to support in the future. Autoscaling requires building some components that are aware of and can communicate the underlying infrastructure APIs (AWS, GCP, Azure, DigitalOcean, OpenStack, etc.) combined with app/host metrics. It's just a matter of putting the implementation effort. We'll get there eventually.

Great stuff - thanks - good luck!

Re: An Open Source, Self-Hosted Heroku

#85

Post by christiangenco »

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…

Try out Flynn for sure, but from my experience with both Dokku is worlds simpler and more stable.

Re: An Open Source, Self-Hosted Heroku

#87

Post by Titanous »

mmanfrin wrote: post #86

Anyone have experience to how this compares with Deis (Workflow)? Last week I spent an evening getting a small cluster set up with kubernetes and deis. It looks to work very similar to Flynn.

When we started in 2013, the only open source scheduler available was Mesos and the ecosystem didn't have community efforts like Kubernetes, so we had to write our own components to build Flynn.

Flynn is designed to be an end-to-end solution for production deployment, and all of our components are created to work together. The whole system is self-bootstrapping and self-hosting, so installation is easy, and the same APIs are used to manage the whole platform as are used to manage apps deployed on it.

In addition to the twelve-factor stateless webapps that Deis Workflow supports, Flynn also includes highly available database appliances with safe, automatic failover (currently PostgreSQL, MySQL, and MongoDB with more coming in the future). We also have a bunch of security features coming over the next few months like Let's Encrypt support and flexible user authentication with 2FA and very granular access control.

If you don't need or want our database appliances and you are comfortable with Kubernetes and happy to install and operate it, then Deis Workflow is a good option. If you don't care about using Kubernetes specifically, Flynn is a good pick as it is easier to get up and running with.

Re: An Open Source, Self-Hosted Heroku

#88

Post by jacques_chester »

Titanous wrote: post #87
mmanfrin wrote: post #86

Anyone have experience to how this compares with Deis (Workflow)? Last week I spent an evening getting a small cluster set up with kubernetes and deis. It looks to work very similar to Flynn.

When we started in 2013, the only open source scheduler available was Mesos and the ecosystem didn't have community efforts like Kubernetes, so we had to write our own components to build Flynn. Flynn is designed to be an end-to-end solution for production deployment, and all of our components are created to work together. The whole system is self-bootstrapping and self-hosting, so installation is easy, and the same…

> When we started in 2013, the only open source scheduler available was Mesos and the ecosystem didn't have community efforts like Kubernetes, so we had to write our own components to build Flynn.

I've taken to referring to this as "Not Invented Yet Syndrome". It's hard to base an architecture on a subsystem that doesn't exist.

Re: An Open Source, Self-Hosted Heroku

#89

Post by tracker1 »

Titanous wrote: post #9
newsat13 wrote: post #5

Earlier quoted context omitted.

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.

For a small-mid sized company with an overworked dev manager, hiring out flynn for the cost of a Jr Systems Administrator sounds pretty reasonable.

Re: An Open Source, Self-Hosted Heroku

#90

Post by mcescalante »

Titanous wrote: post #44
mcescalante wrote: post #32

I'm curious about any compelling reasons I should use something like Dokku or Flynn if I already prefer to manage my own infra with something like Ansible or Salt. Serious question, not a sarcastic rhetorical remark about this type of tool :)

Great question! We designed Flynn to solve a bunch of the common problems around running apps in production. This means that we're working full-time just on the automation and stability of your production environment. As you grow and scale, Flynn will scale with you and provide integrated features without any additional effort. Here's an incomplete list of things that Flynn provides out of the box: - Automatic high a…

Makes sense to me! Thanks for taking the time to write this reply - I'm going to have to play around with Flynn
Post reply on HN