search for: rails_home

...uot;server","framework","lib"].each { |x| $LOAD_PATH.unshift(PACKET_APP + "/#{x}")} +["server","framework","lib"].each { |x| $:.push(PACKET_APP + "/#{x}")} +#$LOAD_PATH.unshift(WORKER_ROOT) +$:.push(WORKER_ROOT) require RAILS_HOME + ''/config/boot.rb'' require "active_record" and adding in "environment.rb" config.load_paths += Dir["#{RAILS_ROOT}/vendor/plugins/backgroundrb/server"] config.load_paths += Dir["#{RAILS_ROOT}/vendor/plugins/backgroundrb/framework&quot...

...'' when BackgroundRB isn''t running throws an exception, which causes problems when executing ''backgroundrb stop'' in a rake task. As a workaround I have modified by ''backgroundrb'' script as follows: when ''stop'' path = "#{RAILS_HOME}/log/backgroundrb.pid" pid = nil begin File.open(path, "r") { |pid_handle| pid = pid_handle.gets.strip.chomp.to_i } pgid = Process.getpgid(pid) Process.kill(''TERM'', pid) Process.kill(''-TERM'', pgid) Process.kill(''KI...

...''d like to submit a patch and am following the steps on this page: http://dev.rubyonrails.org/ Here''s what I did (using mysql 5.0.15-nt): created 2 databases: activerecord_unittest activerecord_unittest2 created 1 user: rails (giving all priveleges to both databases) ran $RAILS_HOME/activerecord\test\fixtures\db_definitions\mysql.sql on activerecord_unittest ran $RAILS_HOME/activerecord\test\fixtures\db_definitions\mysql2.sql on activerecord_unittest2 modified $RAILS_HOME/activerecord\test\connections\native_mysql/connect.rb accordingly I removed all my local changes, so I...

...ke: config.database_configuration_file = "#{RAILS_ROOT}/local/config/ database.yml" But they aren''t picked up in BackgroundRB because Rails ActiveRecord is just initialized directly in MasterWorker#load_rails_env: db_config_file = YAML.load(ERB.new(IO.read("#{RAILS_HOME}/ config/database.yml")).result) Is this an intentional design decision, or just simplest approach tha''s "good enough?" Personally, I''d prefer that my Rails'' environment was initialized the same way in my client application, BackgroundRB server and...

...ch use the active_rbac engine for user and access control. How can I use the original login, etc. forms which were provided with the engine as partials in my application? I''ve tried all of the below mentioned approaches and it seems so that I cannot reach the templates provided under the [RAILS_HOME]/vendor/plugins/active_rbac/app/views directory. # render :partial "active_rbac/login" # render :template "active_rbac/login" So my question is: to be true to the DRY principle, how can i reuse these templates in my layouts? Thanks, Andr?s -- Andr?s Tarsoly tarsolya@gmail.c...

I''m using backgroundrb in a rails project, with packet and chronic unpacked in the vendor folder, to make backgroundrb I''ve added the following line to scribts/backgroundrb $LOAD_PATH << File.join(RAILS_HOME, "vendor") Do you believe it''s a good idea? I don''t like depend on the installed gems ciao ciao paolo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080530/6c24539c/att...

...achment model associated with it are saved to the db, but the file is not uploaded. However, every subsequent file is uploaded successfully with no issues. It seems that maybe the rails environment isn''t being loaded on the first shot, but the load_worker_env.rb file has the line: require RAILS_HOME + "/config/environment" Any suggestions? I''ve tried manually adding ''require aws-s3'' to the load_worker_env.rb file and it didn''t work. Is it maybe something with attachment_fu not getting loaded or maybe the attachment_fu config file? Thanks for the...

Hi - I have a fresh install of OSX, Rails, Ruby, Ferret, AAF etc ... Everything is working fine, I can start mongrel, I can start backgroundrb, but Ferret Drb ... doesn''t want to work. RAILS_ENV=development script/ferret_start Gives me: env: script/runner: Permission denied Is there a way I can debug this to figure out what is going on - or is there another way to start Ferret Drb?

Short update: It seems that the workers go into some state in which they do not have a correct Rails environment (or db connection). When they enter this state it goes wrong all the time :( Joost Hietbrink (YelloYello) wrote: > Hi all, > > We''re experiencing some problems with Backgroundrb. > > Why is "# master_reactor_instance.result_hash = {}" commented in