# Rails and Offline processing

**URL:** <https://www.ruby-forum.com/t/rails-and-offline-processing/84291>\
**Category:** Rails\
**Created:** [March 20, 2006, 8:00pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291 "2006-03-20T20:00:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 8:00pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/1 "2006-03-20T20:00:16Z")

</div>

How are you guys handling threads or server processes that have to,  
for example, process the data in your application on a periodic basis?

Cron jobs can do it and then run on the database. But, are there ways  
to launch threads within the rails application itself.

I have heard of WebBrick ways, but I am working with lighttpd,  
fastcgi? (textdrive if you are really interested).

---

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 8:11pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/2 "2006-03-20T20:11:59Z")

</div>

Look for rails\_cron or script/runner.

–  
– Tom M.

---

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 8:30pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/3 "2006-03-20T20:30:35Z")

</div>

On 3/20/06, Tom M. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > 
> 
> * * *
> 
> Rails mailing list  
> removed\_email\_address@domain.invalid  
> [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)

cron with script/runner. Or in my case (windows), ScheduledTasks.

Works absolutely perfect!

Don’t forget to apply “-e production” to your cron step.

–

---

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 8:45pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/4 "2006-03-20T20:45:04Z")

</div>

Those all look interesting. I wish rails\_cron was a little bit more  
mature. But then again it may work perfectly out of the box.

---

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 9:30pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/5 "2006-03-20T21:30:20Z")

</div>

No, it says it on the wiki page.

---

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 9:06pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/6 "2006-03-20T21:06:31Z")

</div>

Why do you consider it immature?

Because of the revision number?

–  
– Tom M.

---

<div class="post-metadata">

**Author:** ![Berlin\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/838e76/32.png) [@Berlin\_B](https://www.ruby-forum.com/u/Berlin_B)\
**Post date:** [March 20, 2006, 10:36pm UTC](https://www.ruby-forum.com/t/rails-and-offline-processing/84291/7 "2006-03-20T22:36:53Z")

</div>

Good answer! 🙂

–  
– Tom M.