3 ms·
Moe, I don't understand where your hostility comes from. It is fine if you don't like Phusion Passenger, but please don't say things that are untrue. The open
by FooBarWidget 13y ago
Moe, I don't understand where your hostility comes from. It is fine if you don't like Phusion Passenger, but please don't say things that are untrue.
The open source version of Phusion Passenger is not a crippled version. It is used in production by many large users, including New York Times, AirBnB, etc. Your statement that the open source version is "crippled" goes right against the fact that we've been actively developing the open source version ever since Enterprise came out. In fact, open source development has become more active after Enterprise than before, thanks to Enterprise funds. If you check our commits at Github you will see that the rate of development has accelerated. If you take a look at all the new features in the open source version of Phusion Passenger 4 you will see that it is improving at a tremendous rate.
It is not true that the open source Phusion Passenger drops requests and serves 502 errors to users on every single deploy. Upon touching restart.txt, the open source versions blocks requests and resumes them after having restarting 1 process. The blocking only happens for the first process, not for the ones after. At no point will requests be dropped or will errors be served. We even have integration tests in place to check for this. If you see request drops or errors in the open source version, please contact us and we'll have a better look at the problem. If it's a bug, we'll fix, it's that simple.
"popping up shareware nag-screens at random intervals" is completely false. There are absolutely no nag-screens in Phusion Passenger. The open source version of Phusion Passenger is open source, so if you don't believe me, then dig into the source code and tell me where exactly the nag screens are.
The lack of rolling restarts in the open source version is not a secret. Our documentation clearly mentions the differences between the open source and the Enterprise version. With a few clicks, you can find out what the open source version does and does not have.
And actually, the open source version does not "lack" rolling restarts, it just does not automate it for you. You can implement rolling restarts using Phusion Passenger Standalone (open source version!) in the same way you do with Thin and Mongrel, i.e. by swapping sockets. It works fine and some of our users do exactly this. It is just more work than the automated, polished, error-resistant version that Enterprise offers.
And finally, you Unicorn and Puma "fully-functional" while implying that Phusion Passenger is not. This is not true. There are features in the open source version of Phusion Passenger that Puma and Unicorn does not have. The reverse is also true. It is even true that Unicorn has some features that Puma has and vice versa.
- moe 13y agoI don't understand where your hostility comes from. From the dishonest spin that you put on everything you say. I wrote: That's equivalent to popping up shareware nag-screens into my face. You reply with: "popping up shareware nag-screens at random intervals" is completely false. There are absolutely no nag-screens in Phusion Passenger. These little 'misunderstandings' and strawmen add up. Consequently I won't even comment on your further spin-doctoring here. I'll just encourage anyone interested in the matter to also read what EngineYard and UserVoice say about passenger; https://blog.engineyard.com/2012/passenger-vs-unicorn https://blog.engineyard.com/2012/passenger-vs-unicorn https://developer.uservoice.com/blog/2012/08/08/the-dark-passenger/ https://developer.uservoice.com/blog/2012/08/08/the-dark-pas...
- FooBarWidget 13y agoI'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong. Like I said before: errors during redeploy are not supposed to happen even in the open source version, and if they do happen then we are very interested in fixing them. Please tell us more. There is no need to spin this as being "dishonest". If you don't believe us, tell us about your problem, let us fix it, and verify for yourself that it is fixed. Only the facts matter. As for the Engine Yard and Uservoice.com post: 1. All problems that the Engine Yard post talked about, were fixed 2 days after they published that article (http://blog.phusion.nl/2012/09/21/the-right-way-to-deal-with-frozen-processes-on-unix/ http://blog.phusion.nl/2012/09/21/the-right-way-to-deal-with...). If you are still experiencing those problems, tell us, and we'll fix it. By the way, did you notice that EngineYard said something entirely different about Phusion Passenger and Unicorn later on? https://www.engineyard.com/articles/rails-server https://www.engineyard.com/articles/rails-server 2. Almost all problems that that the Uservoice.com talked about, have been fixed in Phusion Passenger 4.0, open source version. 3. There are also plenty of posts that describe migrating from Unicorn to Phusion Passenger, e.g. https://speakerdeck.com/arnvald/dot-dot-dot-but-we-had-to-kill-unicorns https://speakerdeck.com/arnvald/dot-dot-dot-but-we-had-to-ki.... So what does that mean? Experiences differ, for all sorts of reasons, some legit and some not (e.g. inefficient configuration). Neither kinds of posts automatically mean that Unicorn/Phusion Passenger is bad: there will always be people having problems with a particular technology. That's why we encourage people who have problems to contact our support forum.