はてなブックマーク

update (2010) : this resource lifecycle post features two quotes that are enlightening when thinking about state and workflow. update (2011) : a discussion between two engineers about state machines and workflow (guest post at Engine Yard) This post is intended for Ruby developers. The idea for it came after numerous discussions with fellow programmers about state machines and workflow engines. Wh

(note: this blog post is from 2008, ruote evolved a lot since, for an up-to-date “how does ruote work”, see sample workflow run) Well, as “ruote” means “wheel”, it just spins… Ruote being a workflow/BPM engine, interprets process definitions and runs them as process instances. But how does that happen ? The few graphs I’ll use in this post were meant as “embedded documentation” in the HTML renditi

The ruby script here uploads posts to WordPress blogs via AtomPub. Once you’ve set your blog coordinates in the script (around line 20), you can post like that : echo "I love Ruby" | post.rb -t "title" -c "thoughts,ruby" The script will publish your post and then ouptput the WordPress server reply. #!/usr/bin/env ruby # Copyright (c) 2007 John Mettraux # Released under the MIT license # http://www

rufus-scheduler is a thread-based scheduler written in Ruby. It lets you write code like: require 'rufus-scheduler' s = Rufus::Scheduler.start_new s.every '10m' do puts 'open the window for the cat' end s.at '2012-01-01 12:00' do puts 'reminder: wife's birthday' end s.cron '0 22 * * 1-5' do puts 'activate the security system' end s.join # in case of stand-alone script... The main addition brought