similar to: Best cron job method for email notifications?

Just wanted to see if I was using the latest acts_as_solr plugin, but the URL <http://acts_as_solr.railsfreaks.com/> takes me to a GoDaddy domain parking page. Anyone know what''s happened to railsfreaks, and more particularly this plugin? -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org twitter: @hassan -- You received this

LDAP Account Manager (LAM) 5.0 - June 30th, 2015 ================================================ LAM is a web frontend for managing accounts stored in an LDAP directory. Announcement: ------------- LAM Pro can notify your users via cron job that their passwords will expire soon. The Windows support was also enhanced. LAM no longer supports Internet Explorer 8. Full changelog:

Greetings! I could use some advice on which version of BackgrounDrb to use in my current situation. I''ve implemented the initial, single-process multi-threaded version in a previous site, but have no experience with the new version. Current situation is as follows. The application involves personal health information and so has very stringent session management requirements. My

Just received the news from Tom Mornini. Congrats Ezra for the new Engine Yard site and the blog you will be collaborating. Hope to read you there soon. http://www.engineyard.com/ Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060925/3f251fa4/attachment.html

I''m trying to set a multi-value cookie but for some reason it''s not working. Any help would be appreciated. cookies[:user] = { :value => {:email=>params[:login][:email], :passwd=>params[:login][:passwd]}, :expires => 30.days.from_now, :path => "/login"} -- Thiago Jackiw

Hi there, I''ve been experimenting with implementing BackgroundDRb in my rails app but am running into some problems. The primary problem I''m getting is in cleaning up worker threads, or getting any kind of response out of worker threads. If try using the response function/hash in my Worker the worker will not execute reporting that response is an unknown variable or function.

i''m having some problems getting a simple example going with backgrounDRB. after i set my worker to work i try to get back the result like this: w = MiddleMan.worker(key) w.items comes back as DRb::DRbUnknown (i have items as attr_reader in my worker and access it inside there with @items). the result is actually activerecord results in an array. when i change it so my worker puts

I have a form and e file field, and what I''m trying to do is when the file is uploaded, a div shows the uploaded image using ajax, without refreshing the page. But the problem I''m having is that with form_remote_tag it won''t accept :multipart => true. Any ideas? Thanks a lot

Hi *, are there some special settings except of "load_rails: true" to make ActiveRecord models accessible within my workers? I''ve just installed the latest version of this great plugin, but I keep getting undefined method [] for #<DRb::DRbUnknown:0x12345> (line 105 in backgroundrb.rb) when one of the arguments for the worker is an ActiveRecord object. I assume that

I''m trying to run an external Ruby script from my Rails app. To do this i''m using this function def fork_with_new_connection(config, my_class = ActiveRecord::Base) pid = fork do begin my_class.establish_connection(config) yield ensure my_class.remove_connection end end Process.detach(pid) end Then, within my controller I do this:

Hi devs, I was trying to open a new ticket with a minor doc patch at the BackgroundDrb Trac (http://backgroundrb.devjavu.com/) and it seems like only admins have permission to do so. Is this intended? I read in the readme that patches should be mailed to this list, but I much prefer to use Trac since there''s already one set up. Any reason Trac is not open to registered Devjavu users?

Description: ========= This is a fairly simple but handy plugin that lets you specify which database connection to use on a per-model basis. It is useful when you have multiple applications sharing the same data, in other words, this is just a nicer way of using “Model.establish_connection(database)”. Example: ======= First create a ‘shared’ database configuration in config/database.yml: shared:

Hi all, This has been very frustrating for me trying to get this acts_as_ferret working well on a Fedora box. On my mac it works great, no problems with locale, but when I put the code live on my Fedora server, it complains about the locale setting (Error occured at <analysis.c>:498 Error: exception 2 not handled: Error decoding input string. Check that you have the locale set

Hi, I am trying to run Mongrel on win32 to serve an internal rails application. We are accessing legacy data, and some transactions can take 5 to 10 seconds. This is holding up every other request. The -n does not seem to be supported on Win32. Am I missing something, or should I look elsewhere to serve my Rails app on win32? Thanks, Walt -- No virus found in this outgoing message.

So, what''s the status of this project? I''m a little confused. The documentation at http://backgroundrb.rubyforge.org seems out of date. It refers to http://svn.devjavu.com/backgroundrb/tags/release-0.2.1, which doesn''t work. All I want is a way to easily set up tasks that should run periodically. Some stuff should run every 10 seconds, some stuff once a day, etc.

I have an action in a controller that generates and returns a custom png-file, it goes something like this: def custompng #1 gather some userdata from params. #2 make a system call to an advanced java application that renders a png based on the custom data. stores the png on disk. #3 read the png into rails #4 send the png to the browser with method send_data #5 delete the

I just tried writing some controllers, etc. that would allow me to start and monitor background tasks running in new (Ruby) threads, with the idea that I''d eventually manage long-running indexing processes that way. I can kick off such threads OK (by using Thread.new in a routine called by a controller), but it seems like Rails gets huffy if those background tasks and the ordinary

Hi. I'm installed yum-cron and set: # by default MAILTO is unset, so crond mails the output by itself # example: MAILTO=root MAILTO="root at domain.org.ua" I see in log that yum-cron done it's job: # grep "yum" /var/log/cron Aug 11 03:08:02 venti run-parts(/etc/cron.daily)[4516]: starting 0yum.cron Aug 11 03:49:30 venti run-parts(/etc/cron.daily)[4761]: finished

My Rails site uses BackgroundDRb and I have a couple of questions: 1. Can someone point me to some sample code/examples for how to use thread_pool? The website doc says to add a line ====== pool_size 10 ====== in my Worker class which seems straightforward. I wasn''t able to understand this part though: ========= thread_pool.defer(wiki_scrap_url) { |wiki_url| scrap_wikipedia(wiki_url) }

I have a bunch of real uses for BackgroundDrb, but I also a very simple need to delay sending an email for about 5 seconds after a rails action completes. Basically I need to leave time for the DB to commit and sync to the slaves before the email can be sent Is BackgroundDb the right tool for this job? Any other suggestions on ways to implement this? (I have seen suggestions to create a