# What's this called (nuby on rails question)

**URL:** <https://www.ruby-forum.com/t/whats-this-called-nuby-on-rails-question/157574>\
**Category:** Rails\
**Created:** [January 13, 2009, 10:29am UTC](https://www.ruby-forum.com/t/whats-this-called-nuby-on-rails-question/157574 "2009-01-13T10:29:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sweb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@sweb](https://www.ruby-forum.com/u/sweb)\
**Post date:** [January 13, 2009, 10:29am UTC](https://www.ruby-forum.com/t/whats-this-called-nuby-on-rails-question/157574/1 "2009-01-13T10:29:00Z")

</div>

When your server does 1 Ruby operation a day without anyone having to  
visit the site to make it happen. Let’s say the operation would be to  
create an automatic blog post on your blog site every 24 hours. This  
is an example what I am curious about if any RoR code can be run  
without users visiting. Also is this an advanced or beginner’s topic?

Thanks!  
Sam

---

<div class="post-metadata">

**Author:** ![sweb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@sweb](https://www.ruby-forum.com/u/sweb)\
**Post date:** [January 13, 2009, 11:06am UTC](https://www.ruby-forum.com/t/whats-this-called-nuby-on-rails-question/157574/2 "2009-01-13T11:06:14Z")

</div>

Hi,

Based on your OS you can schedule a CRON job/ scheduled task to hit an  
url  
to create a blog etc

NAYAK

On Tue, Jan 13, 2009 at 11:51 AM, Sam W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> >

–

- NAYAK

---

<div class="post-metadata">

**Author:** ![sweb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@sweb](https://www.ruby-forum.com/u/sweb)\
**Post date:** [January 13, 2009, 3:22pm UTC](https://www.ruby-forum.com/t/whats-this-called-nuby-on-rails-question/157574/3 "2009-01-13T15:22:38Z")

</div>

Sam,

I performed an analysis on background processing alternatives (see  
below). I greatly recommend rolling out your own daemon for recurring  
jobs, or using starling+workling for offloading jobs from your rails  
app. Both alternatives are covered in excellent railscasts by Ryan  
Bates.

Cheers, Sazima

```
BACKGROUND PROCESSES
-------------------------------------

```

[http://wiki.rubyonrails.org/rails/pages/HowToRunBackgroundJobsInRails](http://wiki.rubyonrails.org/rails/pages/HowToRunBackgroundJobsInRails)

== Asynchronous Tasks

Launched from Rails request/reponse cycle + optional Message Queueing

- Options  
. ar\_mailer (only for emails) =\> GOOD (only email)  
. starling + workling =\> EXCELLENT  
. Ap4r  
. Spawn / background =\> SIMPLE  
. ActiveMessaging  
. BackgroundFu  
. WorkerQueue  
. Rake in Background =\> SIMPLE  
([#127 Rake in Background - RailsCasts](http://railscasts.com/episodes/127-rake-in-background))

== Recurring Jobs (cron-style)

Scheduled or permanently running in the background

- Options  
. daemon\_generator (rails\_cron) =\> SIMPLE  
[#129 Custom Daemon - RailsCasts](http://railscasts.com/episodes/129-custom-daemon)  
. BackgrounDRb  
. rufus-scheduler =\> GOOD  
. Taskr  
. UNIX Cron and Runner (simple, but consumes resources and you can’t  
controll well)