passenger | 易学教程

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

阅读更多关于 Update new Django and Python 2.7.* with virtualenv on Dreamhost (with passenger)

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 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/python/2.7.3/Python-2.7.3.tgz tar zxvf Python-2.7.3.tgz cd Python-2.7.3 ./configure --enable-shared --prefix=

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

阅读更多关于 Rails 3: Passenger can't find git gems installed by bundler

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 (the Paperclip git gets installed there by bundler install ) in the .htaccess and various places in

Passenger on Windows

阅读更多关于 Passenger on Windows

问题 Is there any way to get Passenger running on a Windows machine? It doesn't appear so, but it seems like many Stackoverflow'ers have used Passenger a lot and I was wondering if its possible . 回答1: Hongli (the author) said in 2008: Hi Mitja. We have no plans to port Passenger on Windows. Windows lacks the proper facilities to implement Passenger efficiently. Passenger on Windows will be very, very inefficient, which can give both Ruby on Rails as well as Passenger a bad name. So to me it looks

Broken precompiled assets in Rails 3.1 when deploying to a sub-URI

阅读更多关于 Broken precompiled assets in Rails 3.1 when deploying to a sub-URI

问题 I'm in the process of updating a Rails 3 app to use Rails 3.1 and as part of that, am making use of the new asset pipeline. So far, I've got everything working apart from one rather annoying problem I can't solve. The application and all its assets works fine in development, but in production it is deployed to a sub-URI using Passenger ( http://the-host/sub-uri/ ). The problem with this is that the assets are pre-compiled during deployment and one of my CSS (well, it's a .css.scss file) files

Setting up Rails app on Apache with passenger - Rails doesn't seem to load

阅读更多关于 Setting up Rails app on Apache with passenger - Rails doesn't seem to load

问题 I am trying to set up Rails on a Ubuntu instance by following along with documentation such as https://help.ubuntu.com/community/RubyOnRails. I am trying to set up the app from the Rails Getting Started page here: http://guides.rubyonrails.org/getting_started.html. What I have done so far: Installation of Ruby/RubyGems/Rails through RVM and GEM (this installed Ruby 1.9.2 and Rails 3.0.7) Installation of the mysql and mysql2 module (latter which didn't work) Creation of rails app (blog app as

Can my /public directory be a symlink with rails 3 + passenger 3 + nginx 0.8?

阅读更多关于 Can my /public directory be a symlink with rails 3 + passenger 3 + nginx 0.8?

问题 I'm putting together a rails deployment where the public directory is a symlink to another directory on the system. This is with passenger 3 on nginx .8. It does't seem to like that setup. Nginx always follows symlinks by default, so AFAIK it's not a matter of doing the equivalent of Apache's +FollowSymLinks. update Looks like this is covered here: http://www.modrails.com/documentation/Users%20guide%20Nginx.html#application_detection Note that Phusion Passenger for Nginx does not resolve any

Passenger/mod_rails fails to initialize in Fedora 12 when starting Apache

阅读更多关于 Passenger/mod_rails fails to initialize in Fedora 12 when starting Apache

问题 I am in the process of setting up a server to run a Ruby on Rails application on Fedora 12, using Passenger. I am at the stage where I've installed Passenger, set it up as prescribed, but get the following errors when I restart Apache: [Wed Jan 13 15:41:38 2010] [notice] caught SIGTERM, shutting down [Wed Jan 13 15:41:40 2010] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0 [Wed Jan 13 15:41:40 2010] [notice] suEXEC mechanism enabled (wrapper: /usr

Passenger: internal server error

阅读更多关于 Passenger: internal server error

问题 I installed Apache, Passenger and Sinatra and deployed an app. It gives error when trying to access: An error occurred while starting up the preloader: it did not write a startup response in time. Application root /var/www/html/test Environment (value of RAILS_ENV, RACK_ENV, WSGI_ENV and PASSENGER_ENV) production Ruby interpreter command /usr/local/bin/ruby User and groups Unknown Environment variables Unknown Ulimits Unknown How can I solve it? Edit In the application log, I found this line

403 Forbidden on Rails app w/ Nginx, Passenger

阅读更多关于 403 Forbidden on Rails app w/ Nginx, Passenger

First off, apologies: I know the 403 Forbidden question is a common one for Rails/Nginx installs, but none of the answers I've read so far have solved it for me. Disclaimer: This is my first time deploying a Rails app somewhere that isn't Heroku. Please be gentle. ;) Situation: I have a Rails app running on an Ubuntu 12.04 server, running Nginx (installed with Passenger). I've deployed my app to my server correctly, but when I attempt to access the site, I receive a 403 Forbidden error. Checking my error logs, I see: 2013/10/23 22:47:01 [error] 27954#0: *105 directory index of "/var/www

We're sorry, but something went wrong. - with Rails, Apache, Passenger

阅读更多关于 We're sorry, but something went wrong. - with Rails, Apache, Passenger

问题 I have Rails 3.2.3 with Apache and Passenger . I have a project working in development mode. When I switch the project to production mode ( Passenger standard) it gives me an HTTP Error 500 : We're sorry, but something went wrong. This happens even with WEBrick . Can somebody help me? Edit : My production environment file: http://pastebin.com/ZAudSzkc 回答1: Make sure you have ran $ bundle install . If this doesn't succeed, go to your production environment and connect to your server using ssh