similar to: Constants defined in initializer not found when running gems:install in test

I am doing some testing with the rails trunk, version I switched to because of memory leaks in 0.13.1 under linux environment. Right now the application is running fast and steady under linux, with no memory leaks using SCGI Rails Runner 0.4.3 from Zed, BUT it has become unusable under Windows (our main development environment) where I am getting a lot of segmentation faults. BUT the problem

Hi all, I set up a standard Capistrano deployment on a new host. To start the Mongrels, "script/spin" calls "script/process/spawner mongrel". It prints a few lines as if everything were normal, however the mongrels are not started and it doesn''t create any files in log or tmp that would give me a clue on what happened. If I start Mongrel via script/server -e

Like most, I have a test and a production env. Both are CentOS 5, Ruby 1.8.6, Rails 2.0.2, MySQL 5, and Apache. Both were setup using the same procedure. Except for the hardware (test: Intel, prod: AMD) and memory (test: 512M, prod: 1G), both systems are essentially the same right down to the Rails env. Unfortunately, memory usage is very different for each. The test system has 2 mongrel

I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3 beta gem. ?Firing up unicorn_rails spews "RAILS_ENV not defined by config/boot". ?I know this is likely a result of RAILS_ROOT being deprecated?in Rails 3 but I can''t seem to config my way around it. I''m sure other people must have run into this before. ?Is there a quick fix? Thanks

Hi everybody, Please any one help me, Previous two day''s I am googling, Still not find solution. this really frustrating. I had deploy my app on heroku http://radiationn.heroku.com/. it is working fine on localhost but i got APPLICATION ERROR. IN log wht i find that in photo.rb model not able to find "has_attached_file", I am not able to shout out this proble. It working

Has anyone managed to replace ActiveRecordStore::Session with their own model? In the source (http://dev.rubyonrails.org/browser/trunk/actionpack/lib/ action_controller/session/active_record_store.rb) it says you can override the default by setting CGI::Session::ActiveRecordStore.session_class = MySessionClass I have tried doing this in a number of ways but I get all kinds of weird errors, as

i don''t get what is going on here. if i run the restclient command that starts an irb with restclient it works fine but when i try to load it from environment.rb with require ''rest_client'' this is what i get... it''s driving me batty. /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'': no such file to load --

I''m running Redmine on Ruby, and attempting to load a new plugin. When I attempt to run the command: rake db:migrate_plugins RAILS_ENV=production It fails with this error: rake aborted! no such file to load -- initializer /var/www/redmine/config/boot.rb:65:in `require'' /var/www/redmine/config/boot.rb:65:in `load_initializer'' /var/www/redmine/config/boot.rb:43:in

I''ve found a conflict in the way the configuration file is handled, in particular effecting the setting of the ENV[''RAILS_ENV''] value. When I attempted to run a worker in production, it would run fine the first time - the second time would fail because it was trying to access the development database. I had created a ''backgroundrb_prodcution.yml'' file

Hi, I''m getting the next errors, would anyone have any suggestions? Thanks. [~/rails/hip]# rake --trace db:migrate RAILS_ENV="production" (in /home/domain/rails/hip) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! undefined method `empty?'' for nil:NilClass /usr/lib/ruby/1.8/erb.rb:469:in `scan''

Hey all, I''m having some issues moving a project that incorporates Backgroundrb onto a staging server... For some reason (surely of my own doing), my RailsBase workers are insisting on using trying to access my development DB instead of my "production" DB. When I try to load a model object from within a worker, I get the following: 20061120-21:54:28 (26296)

This is what I have inside a rake task. In this rake task I need to call another rake task called email:send_messages. However I need to pass the RAILS_ENV as ''staging''. Rake::Task["rake:email:send_messages"].invoke I tried a lot of variations but none of them work. Rake::Task["rake:email:send_messages"].invoke RAILS_ENV=staging

All, Just read in the Capistrano manual about the Capistrano "migrate" task. There it says that: "By default, all this task does is change to the directory of your current release (as indicated by the current symlink), and run rake RAILS_ENV=production migrate. You can specify that it should run against the latest release (regardless of what the current release is) by setting

Not sure this is known behaviour but it seems that if want to set the environment to, for example, test, and you want to use Active Record you have to both explicitly set the RAILS_ENV and the BackgrounDRb environment. So, if you have a config file backgroundrb_test.yml (as well as the default) and set the environment to test in that, this is what *seems* to happen: $

I have been strugging with getting backgroundrb to stay in the correct environment using multiple configuration files and the -c switch when starting backgroundrb. If I start brb like this: ./script/backgroundrb run RAILS_ENV=development -- -c ../config/development_background.yml where development_background.yml specifies "development" for rails_env and environment, the first worker

I get the error below when I try to start my server. Here are the versions installed: OS: Windows Server 2008 Ruby: 1.8.7 Gems: actionmailer (2.3.5, 1.3.5) actionpack (2.3.5, 1.13.5) actionwebservice (1.2.5) activerecord (2.3.5, 1.15.5) activeresource (2.3.5) activesupport (2.3.5, 1.4.4) cgi_multipart_eof_fix (2.5.0) daemons (1.0.10) gem_plugin

Hi folks, I''ve experimented a problem while deploying my app, I''ve sent the HUP signal to the master process, I''ve checked everything is ok: new master and workers are spawned and the old ones are killed(I''ve checked the PIDs), but the new code deployed isn''t reflected in the living site, so I''ve to stop and start again unicorn in order to see

On the wiki it says to migrate your DB to production, you can run: rake migrate RAILS_ENV="production" This is taken from: http://wiki.rubyonrails.com/rails/pages/UnderstandingMigrations My database is set up with correct MySQL permissions granted and the database.yml is pointing at it. I get no errors when I run it, but equally my production database does not change at all.

Hello! I want to use the same application in two environments (production and development) on the same server (apache2 with fcgid) in different (aliased) directories. Is there a way to specify RAILS_ENV inside my <Directory> directives? I have the line DefaultInitEnv RAILS_ENV production in my httpd.conf but I want one of the directories to be development. Setting the ENV var directly in

Hello, I want to put my app in production mode. So I write this line in environment.rb : ENV[''RAILS_ENV''] = "production" I restart webrick. If I write <%= ENV.inspect %> I have the correct "RAILS_ENV"=>"production" But browse my site and look the log, the development.log is still growing and the production.log stay to 0 ko