Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Simple daemonized pseudo-scheduler controlled by rake tasks
Ruby JavaScript
Branch: master

trying to fix tests

latest commit ab13032edd
Danil Pismenny authored
Failed to load latest commit information.
lib * Minor bugs fixed
rails LoopDance::Controller / Commands / Railtie and Task released
rails_example Version bump to 0.4.0
tasks bug fixed
.document Initial commit to loop_dance.
.gitignore README changed
.rvmrc trying to fix tests
Gemfile trying to fix tests
LICENSE.txt Initial commit to loop_dance.
README.rdoc foreverb as alternative
Rakefile trying to fix tests
VERSION Version bump to 0.5.3
init.rb LoopDance::Controller / Commands / Railtie and Task released
loop_dance.gemspec Regenerate gemspec for version 0.5.3



No forks. No threads. Just looped pseudo-scheduler based on `daemon_controller` and `looper`.

One dancer is one daemon.

Easy to install

gem 'loop_dance'

Simple to setup

Create file 'lib/dancers.rb':

class Dancer1 < LoopDance::Dancer

  every 3.hours do

  every 60.seconds do


Useful management

From the rails application:

Dancer1.start unless Dancer1.running?

By the rake tasks:

rake loop_dance:start_all
rake loop_dance:stop_all
rake loop_dance:status

rake loop_dance:dancer1:start
rake loop_dance:dancer1:stop
rake loop_dance:dancer1:status


class Dancer1 < LoopDance::Dancer
  mute_log  true       # mute redundant logging, just start, stop and errors
  autostart true       # enable autostart at rails server startup. False by default

  # Don't trap signals. True by default (trapped)
  trap_signals false

  # daemon_controller`s options
  start_timeout   60            # 15 by default
  stop_timeout    60            # 15 by default
  log_file_activity_timeout 17  # 7 by default



Contributing to loop_dance

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch

  • Commit and push until you are happy with your contribution

  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.


Copyright © 2010-2011 Danil Pismenny. See LICENSE.txt for further details.

Something went wrong with that request. Please try again.