passenger

deploying rails3 apps with bundler and phusion passenger: .bundle dir not found

青春壹個敷衍的年華 提交于 2019-11-27 13:27:31
问题 i am trying to deploy rails3 apps with the latest phusion passenger 2.2.11 and ruby-enterprise-1.8.7-2010.01. i am using bundler, but passenger seems to not be able to find the .bundle dir. error message: git://github.com/rails/rails.git (at master) is not checked out. Please run `bundle install` (Bundler::PathError) where do i install the .bundle? where do i tell passenger which bundle to use? any hints? thanks! 回答1: i think the command you are searching for is bundle pack which will move

The website is under heavy load + ROR

北战南征 提交于 2019-11-27 11:12:21
问题 We are running a website with ROR on CentOS 6 with 2 web server and 1 database server. Some times it shows message "The website is under heavy load"... Can some plese help you what to check here. We are using Passenger 4.0.21 with Ruby 1.8.7 and Apache 2.2.15. Web server is running with the default settings. Below is some output of passenger-status: # passenger-status Version : 4.0.21 Date : Thu Dec 12 02:02:44 -0500 2013 Instance: 20126 ----------- General information ----------- Max pool

Capistrano to deploy rails application - how to handle long migrations?

你说的曾经没有我的故事 提交于 2019-11-27 09:26:04
问题 So I am using Capistrano to deploy a rails application to my production server (apache+passenger) and at the moment deployment usually goes along the lines: $cap deploy $cap deploy:migrations It got me wondering, let's say my db:migrations took a long time to execute on the production server (a big refactor of the db schema) - in this case what is best practice with Capistrano? What happens if users are connected to my application at the time of deployment? Should I gracefully send users to a

Nginx configuration leads to endless redirect loop

拥有回忆 提交于 2019-11-27 07:06:29
So I've looked at every sample configuration I could find and yet every time I try and view a page that requires ssl, I end up in an redirect loop. I'm running nginx/0.8.53 and passenger 3.0.2. Here's the ssl config server { listen 443 default ssl; server_name <redacted>.com www.<redacted>.com; root /home/app/<redacted>/public; passenger_enabled on; rails_env production; ssl_certificate /home/app/ssl/<redacted>.com.pem; ssl_certificate_key /home/app/ssl/<redacted>.key; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X_FORWARDED_PROTO https; proxy_set_header X-Forwarded-For $proxy_add

Unable to start the Phusion Passenger watchdog?

五迷三道 提交于 2019-11-27 05:22:23
问题 I have done a Phusion Passenger setup on Ubuntu 10.04, with Apache2. Whenever I restart the Apache server I got the following error message, and the Rails application is not running. [error] *** Passenger could not be initialized because of this error: Unable to start the Phusion Passenger watchdog because its executable (/usr/lib/phusion-passenger/agents/PassengerWatchdog) does not exist. This probably means that your Phusion Passenger installation is broken or incomplete, or that your

Error while loading shared libraries: 'libpcre.so.0: cannot open shared object file: No such file or directory'

房东的猫 提交于 2019-11-27 05:17:43
问题 I just installed Passenger 3.0.11 and nginx and got this error: Starting nginx: /opt/nginx/sbin/nginx: error while loading shared libraries: libpcre.so.0: cannot open shared object file: No such file or directory 回答1: The message means what it says. The nginx executable was compiled to expect the PCRE (Perl-compatible Regular Expression) shared library to be available somewhere on LD_LIBRARY_PATH or specified in /etc/ld.so.conf or whatever equivalent library-locating mechanisms apply to your

Update new Django and Python 2.7.* with virtualenv on Dreamhost (with passenger)

和自甴很熟 提交于 2019-11-27 05:04:22
问题 Dreamhost is a great host for small project. And it's also Django friendly hosting. Everything good except python and Django version is a little bit out of date. Well it's a whole day of work to figure out how to update Python 2.7.3, Django 1.4 on dreamhost and I really want to share with whoever finding it 回答1: I currently have private server, a shell account and a bit of luck. So here is what I do: SSH to your host to upgrade python cd ~ mkdir tmp cd tmp wget http://www.python.org/ftp

“Incomplete response received from application” from nginx / passenger

纵饮孤独 提交于 2019-11-27 02:55:59
I tried to deploy my rails app on nginx and ubuntu via capistrano like the tutorial on the page https://gorails.com/deploy/ubuntu/14.04 . but at the end i get an error message: Incomplete response received from application in my browser. this is probably an error from passenger, but how can i figure out what to do? Yaniv Vova Alterman Your rails_env production don't have required set up,probably missing secret_key_base. Open /etc/nginx/sites-available/default and change the rails_env to development: rails_env production; to rails_env development; If the app is loading it's not a passenger

Rails 3: Passenger can't find git gems installed by bundler

社会主义新天地 提交于 2019-11-26 23:52:18
问题 Rails 3.0.0, Passenger 2.2.15: Create a new Rails project Add gem 'paperclip', :git => 'git://github.com/lmumar/paperclip.git', :branch => 'rails3' to your Gemfile Do bundle install Everything OK, starting with rails/script server & accessing also works However, when accessing with Passenger, it says: git://github.com/lmumar/paperclip.git (at rails3) is not checked out. Please run bundle install (Bundler::GitError) I have tried bundler pack (doesn't help) and setting BUNDER_HOME to ~/.bundler

Nginx configuration leads to endless redirect loop

怎甘沉沦 提交于 2019-11-26 13:03:06
问题 So I\'ve looked at every sample configuration I could find and yet every time I try and view a page that requires ssl, I end up in an redirect loop. I\'m running nginx/0.8.53 and passenger 3.0.2. Here\'s the ssl config server { listen 443 default ssl; server_name <redacted>.com www.<redacted>.com; root /home/app/<redacted>/public; passenger_enabled on; rails_env production; ssl_certificate /home/app/ssl/<redacted>.com.pem; ssl_certificate_key /home/app/ssl/<redacted>.key; proxy_set_header X