<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>corobo</author><text>I&amp;#x27;ve been using Flynn for a while now. Unfortunately there&amp;#x27;s always something that entirely bricks the cluster eventually. Sometimes a node will reboot unexpectedly (as happens with servers) and the cluster slowly implodes from there, sometimes I&amp;#x27;ll just get a monitoring alert that all the sites hosted on it have gone down for no apparent reason.&lt;p&gt;They announced during their 1.0 release that Flynn is now production ready but I have to disagree at this time. I do honestly love the idea of running my own Heroku but it&amp;#x27;s just not stable enough and doesn&amp;#x27;t recover well if a node goes offline without manual intervention using the flynn-host fix command (and sometimes that command just chokes up completely).&lt;p&gt;Next time it happens (when, not if, at this rate) I&amp;#x27;ll try to set aside some time to gather up the logs to help debug the problem but I&amp;#x27;m using Flynn to avoid the sysadmin side of things and just build my product. In my opinion Flynn is tinker-ready, not production-ready. It&amp;#x27;s infuriating that it has these random problems because like I say I really _really_ love the product and desperately want to be able to use it reliably.</text><parent_chain></parent_chain></comment><story><title>Flynn: open source PaaS</title><url>https://flynn.io/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>erowtom</author><text>Experienced Flynn last year, we spent about 2 weeks making it work properly with our solution (We had a complex SaaS solution hosted on Heroku, with tons of addons).&lt;p&gt;We had some very bad bug that happened at the time (like deploying a new version made the dyno crash and we had to deploy a completly new environment).&lt;p&gt;Other than pretty bad bug, it was working properly, and did what they sell.&lt;p&gt;Good point is that the dev team is very responsive and we reported a bunch of bug that got fixed in no time. They also have a smooth updater when a new Flynn release came out, side bad note is at this time, it was kinda bugged (because of our specific setup).&lt;p&gt;For all those reasons, we choose to stick with Heroku at that time (we also tried Doku &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dokku&amp;#x2F;dokku&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dokku&amp;#x2F;dokku&lt;/a&gt;, various AWS services such as BeanStalk,  and DEIS &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;deis.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;deis.io&amp;#x2F;&lt;/a&gt;), but for sure it was the best candidate out there and I would love to give it a try again.</text><parent_chain></parent_chain></comment><story><title>Flynn: open source PaaS</title><url>https://flynn.io/</url></story>