passenger

Password protecting Rails site running on Nginx and Phusion Passenger

风格不统一 提交于 2019-11-30 18:34:15
I want to protect my newly deployed Rails 3 app with the basic http authentication. It's running on the latest Nginx/Passenger and I'm using the following Nginx directive to protect the web root directory: location = / { auth_basic "Restricted"; auth_basic_user_file htpasswd; } htpasswd file was generated using Apache htpasswd utililty. However, after entering correct username and password I'm getting transferred to the 403 Forbidden error page. Analyzing Nginx error log revealed this: directory index of "/var/www/mysite/public/" is forbidden, client: 108.14.212.10, server: mysite.com, request

Sidekiq worker not getting triggered

被刻印的时光 ゝ 提交于 2019-11-30 17:21:08
I am using Sidekiq for my background jobs: I have a worker app/workers/data_import_worker.rb class DataImportWorker include Sidekiq::Worker sidekiq_options retry: false def perform(job_id,file_name) begin #Some logic in it ..... end end Called from a file lib/parse_excel.rb def parse_raw_data #job_id and #filename are defined bfr DataImportWorker.perform_async(job_id,filename) end As soon as i trigger it from my action the worker is not getting called.. Redis is running on localhost:6379 Any idea why this must be happening. The Environment is Linux. basgys I had a similar problem where Sidekiq

Could not find rake-10.1.0 in any of the sources

旧时模样 提交于 2019-11-30 15:26:36
I have been working with rails and have been trying to setup passenger with rake 10.1.0 and it sends back me this errors. Here is the link to the error. Website LInk It looks like Bundler could not find a gem. This is probably because your application is being run under a different environment than it's supposed to. Please check the following: * Is this app supposed to be run as the `rails` user? * Is this app being run on the correct Ruby interpreter? Below you will see which Ruby interpreter Phusion Passenger attempted to use. * Are you using RVM? Please check whether the correct gemset is

Is it possible to change Passenger Ruby version without recompiling?

时光毁灭记忆、已成空白 提交于 2019-11-30 12:51:19
I tried changing the default ruby command to 1.9.2 but Passenger keeps running 1.8.7 Is Passenger compiled with Ruby embedded? To set the Ruby version add this line to your vhost file: PassengerRuby /path/to/the/ruby/version/you/want/to/use Whenever a "bundle update" updates the version of the passenger gem, I do sudo su - passenger-install-apache2-module At the end of that process, it spits out the full blob of stuff that you need to put at the top or your Apache config. E.g. something like: LoadModule passenger_module /usr/local/rvm/gems/ruby-1.9.2-p180@rails31/gems/passenger-3.0.9/ext

Why should I care about RVM's Gemset feature when I use Bundler?

丶灬走出姿态 提交于 2019-11-30 10:27:14
问题 I just don't get it. I thought, Bundler was developed to resolve version conflicts between gems. So that I just have to require "bundler/setup" and everything is fine, knowing that Bundler will load the correct versions of all my gems and their dependencies. Now, RVM is great for managing multiple Rubies, I know, but why should I care about the Gemset feature? Do I miss something here? Can it make my development even easier? Maybe, some of you can give me some hints on the perfect RVM +

Phusion passenger-status: what value for passenger_instance_registry_dir?

拜拜、爱过 提交于 2019-11-30 08:34:45
I've done a new install of nginx 1.6.3 and passenger 5.0.15 on Ubuntu 14.04 from source in order to add tracing components from AppNeta for my ROR 4.2 app on one of my servers. Nginx and passenger are running and serving pages. I am getting the trace data for server monitoring. All seems well, However, when I run "passenger-status" (as root), I get the following: ERROR: Phusion Passenger doesn't seem to be running. If you are sure that it is running, then the causes of this problem could be: You customized the instance registry directory using Apache's PassengerInstanceRegistryDir option,

Phusion Passenger is throwing errors after upgrading Ruby and Rails using rvm

落爺英雄遲暮 提交于 2019-11-30 08:34:17
I recently upgraded my Rails setup to 3.1.3 and I'm having issues with Phusion Passenger loading an older app on this server. I got everything running on a testapp but I'm still having issues with this one app. When I run the Webrick server on port 3000 my app runs perfectly but when attempting to access it through the virtual host I continue to get Passenger errors. Here's the info: Error being thrown by Passenger Ruby (Rack) application could not be started Error message: Could not find activesupport-3.0.7 in any of the sources (Bundler::GemNotFound) Exception class: PhusionPassenger:

Apache's limit to POST request size

◇◆丶佛笑我妖孽 提交于 2019-11-30 07:25:56
问题 Is there any limit of the POST request size in apache? What is the default value of this limit and is there any way to increase it? If it matters, Rails application is started on this server using passenger. 回答1: The limit in Apache is set via the LimitRequestBody directive and defaults to 0 : This directive specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2GB) that are allowed in a request body. Take a look at the full description of Apache's LimitRequestBody directive

Rails 3.1, nginx, Passenger directory index forbidden

。_饼干妹妹 提交于 2019-11-30 06:58:03
问题 I'm getting the following error in nginx (with a 403) when I visit .com: [error] 5384#0: *1 directory index of "/u/apps/<app-name>/current/public/" is forbidden I'm on Ubuntu 10.04 and I can't for the life of me get nginx, Passenger, Rails 3.1, and Capistrano to play nicely. I'm deploying to /u with Capistrano. Everything in /u is 755, owned by the app user. /u/apps//current/public/ has all my assets, the favicon, and everything else you'd expect. When I add autoindex on to nginx.conf I get a

Routing Error with Post/Put requests (Passenger Headers)

旧巷老猫 提交于 2019-11-30 05:37:32
问题 I've run into a weird problem and after a bunch of research can't get any closer. I've got several forms that upload files via Carrierwave. When I upload the information, part of the route gets cut off (I think). For example, I have a multi-part form submitting to: https:/domain/programs/223/add_file as POST but on submission I get the error No route matches [POST] "/223/add_file" even though what's in my address bar is the complete route. And if submit the complete route as a GET request it