[Rails] creating objects in record filters is not a good idea

After some research, I moved the creation of the associated objects to the controller#create, where it belongs, really, and the code worked. I was getting contradictory results in the console because I was using the after_save filter. At first, the various builds/associations done in the after_sav

[Rails] associations seemed saved in console, but aren't

I have a Course model: class Course < ActiveRecord::Base belongs_to :interaction_outline, :class_name => "Tree", :foreign_key => "interaction_outline_id" belongs_to :token_outline, :class_name => "Tree", :foreign_key => "token_outline_id" after_save :make_outlines def make_outlines

[Rails] BackgroundRB for multiple parallel tasks: thread or worker?

I'm just getting started with BackgroundRB, but I'm not sure how to do what I need to do. I have many chat rooms (Jabber) which are controlled or mediated by a Rails app. There are periodic elections carried out in these rooms. Just this would be easy. I could set up a chron job in the configura