Would love to see mod_rails officially supported, replacing the current implementation of mongrel.
Would love to see mod_rails officially supported, replacing the current implementation of mongrel.
Especially since passenger could support the much simpler Sinatra framework in addition to Rails.
I desperately need mod_rails, I'm losing business to heroku.
If you see how fast heroku is growing, you can easily see how big this market is.
PLEASE!
We have been using cPanel on our servers for several years - but we are moving all of our sites over to ROR3, which is not yet supported by cPanel. Unfortunately that means our next server will not be using cPanel, and our old servers will be decommissioned.
We don't want to say goodbye to cPanel (!) so would be grateful if you could add ROR3 support as soon as is feasibly possible![]()
8 months later... any progress on this?
ARRRRGHHHH! I spent the afternoon upgrading a rails app from 2.3.5 to 2.3.11 only to discover Mongrel is not compatible with any rails after 2.3.7 ( Friendly warning: Mongrel doesn't work with rails 2.3.8 ) Had to downgrade the app back to 2.3.5 to get it working. Thank god for git.
cPanel, you really need to get going on passenger support. Rails 3.1 is right around the corner. It's almost a joke to say that cPanel supports rails because it's so far behind the current version.
This is an excellent idea, we need rails 3 support!
You can get Mongrel to work with Rails 2.3.8 and 2.3.11 if you add the following to /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/cgi.rb file:
You'd place the above two lines immediately before this line in that file:Code:@head['cookie'] = options['cookie'] if options['cookie'] options.delete('cookie')
I have a case #45774 opened about that issue to have our rails versions we install (previously 2.3.8 and now 2.3.11) patched for that issue. The above issue being that cookies aren't properly passing the header type to the redirected Apache page, so the mongrel page will work on the port but the redirected page for Apache port 80 will not work (it shows either a blank page or the coding content instead).Code:REMOVED_KEYS.each {|k| options.delete(k) }
Of note, I've tested Rails 2.3.7 and found the same issue happening for the cookies not being passed with the proper header type on it as well with Mongrel, so I highly doubt that using Rails 2.3.7 will correct the issue. I think it's simply a bug with Mongrel working properly at this point period.
I also recently found another issue with Mongrel in regards to blank pages showing even on the domain.com : port# url due to something else where it doesn't work on the cPanel setup (I don't entirely know the cause of this bug but it isn't exactly the same as the other one for cookies and until I have sufficient information I cannot open up a report about it). However, that issue is corrected by using this content:
https://gist.github.com/471663
You'd create a file at /home/username/rails_apps/appname/config/initializers/mongrel.rb location with the content from that code on the page in question. Please replace username with the cPanel username and appname with the Rails application name.
cPResources: Support Options | More Support Options | Forums Search | cPanel.net Site Search | Mailing Lists(Alt) | Docs
-- Tristan, Forums Technical Analyst, cPanel Tech Support
Submit a ticket | Check an existing ticket
+1
Rails 3 is coming up fast and I cannot support sites who need it.
+1 vote for Rails 3 support. I think mod_rails is the best solution for cPanel implementation.
█ WebTuga Hosting
█ Portuguese Shared, Virtual and Dedicated Web Hosting
█ Providing the best solutions for you!