Follow these instructions from resque readme (apache, ngnix) and check out current resque repo. Now update following two files:
1. Add gem "resque-scheduler","2.0.0.d" to Gemfile
2. Run bundle
3. Add require 'resque_scheduler' to config.ru

Restart you webserver and are ready to go – Happy scheduling!

Both file after editing:

#!/usr/bin/env ruby
require 'logger'

$LOAD_PATH.unshift ::File.expand_path(::File.dirname(__FILE__) + '/lib')
require 'resque/server'

# Set the RESQUECONFIG env variable if you've a `resque.rb` or similar
# config file you want loaded on boot.
if ENV['RESQUECONFIG'] && ::File.exists?(::File.expand_path(ENV['RESQUECONFIG']))
  load ::File.expand_path(ENV['RESQUECONFIG'])
end

require 'resque_scheduler'
                                           
use Rack::ShowExceptions
run Resque::Server.new

source :rubygems

gemspec

group :test do
  gem "rake"
  gem "resque-scheduler","2.0.0.d"
  gem "rack-test", "~> 0.5"
  gem "mocha", "~> 0.9.7"
  gem "leftright", :platforms => :mri_18
  gem "yajl-ruby", "~>0.8.2", :platforms => :mri
  gem "json", "~>1.5.3", :platforms => :jruby
end

This weekend was Rails 3.1 Hackfest. The rails community was called to test the upcoming version 3.1 to its limits, to find bugs and or flaws and get it polished for the final release. So I did:

I’m working with the rails 3.1 since it first release candidate, but never tried in production. So I made my task to finally test this, and bring my app in the wild – on my (not root) server. Rails 3.0 is running there smoothly so I didn’t expect any problems – wrong!
Show stopper was the Javascript Runtime dependency on production. Reason was quickly found: Coffee-Script – ahrg! It depends on ExecJS, which depends on a Javascript Runtime. Unfortunately, and that’s because I’m not on a root server, I got neither node.js, therubyraser, Mustang nor Johnson installed there.

I read this article, which supposed to precompile the assets – didn’t help either and runtime is needed again.

In the End, the solution was as simple as obvious: just don’t use coffee-script in production I did, removed the coffee-script gem form my Gemfile – and tatatata: it works! Uhh! This took me quite a long time to get it right. Javascript Runtime dependecy no good for prodcution, and reading Mr. Katz it’s looking good to get this fixed for the final release – uff! Happy so get tin final one soon! Yeah!

[cheesey image taken from PragDave - thx]

I was quite annoyed by the wasted time it took each time I grep the rails routes table.
Wait, can’t this be cached? – Sure it can!
So I came up this nice little alias to cache the output once:

alias route='CF=tmp/routes_cache; [[ ! -s $CF ]] && rake routes > $CF; cat $CF | grep '


now it’s ultra fast, try e.g.:

$ route root

bang!

Click here to view the embedded video.

Oldies, but Goldies: ‘Methodfinder’ is a really nice extension for your ruby/rails irb and shipped with the ‘what_methods’ gem. I’m using quite a lot and can’t go without it anymore (aka. I’m too stupid to remember all those method names .

gem install what_methods

http://redhanded.hobix.com/inspect/stickItInYourIrbrcMethodfinder.html

See more hints by Dr. Nic blog here

After having enjoyed a wonderful summer with lot of travels and being in more or less ‘offline’ mode, I’m back ‘online’ and I started my new Job at soundcloud.com.

It’s like Fickr but for Music – upload your tracks and share them among the community and fans.

It’s kick ass! Take a look around the office, check this out: http://www.wechsellook.com/post/read/90

So I developed a tiny command line client, which allows you to send request easily. It comes as a gem and easily to install:

gem install oauth-cli

After installation, execute oauthc. You either make onetime calls, with giving all required data as parameter, or just go into interactive mode, to get a shell for multiple calls and history. For not stating all connection data over and over again, it comes with multiple profile support, a wizard to create those easily and presets for Twitter and Qype.

See this nifty example call:
oauthc -p twitter get statuses/friends.json

I hope you like it – Bug reports, suggestions, updates go to:

http://github.com/rngtng/oauth-cli/issues

See Readme:

http://github.com/rngtng/oauth-cli/blob/master/README.rdoc

See Source:

http://github.com/rngtng/oauth-cli

For that, I needed Serial communication within ruby. Thanks to ruby-serialport first steps went quite well. I could write OR read from and to Arduino easily. But for some reasons, writing AND reading using the same instance didn’t work out.

I used a simple ‘send-input-back’ sketch on the Arduino side. So every byte I’m sending is returned back. I checked with the Arduino IDE Serialmonitor and a simple Processing script – everything worked alright. But using ruby it was different. Writing to serial port worked okay, but reading from it was just random. Sometimes I read the response, sometime I didn’t – really, really weird. Some headaches and a lot of time testing I finally found the solution: just open two instances of the serial port. One for sending, one for reading – and, surprise, surprise – it works perfect! Who would have guessed that!? Strange..

// To be completed
require 'serialport'
port_write = Serialport.new()
port_read = Serialport.new()

Ok, continuing hacking, more soon…

module Kernel
   private
   def this_method
     caller[0] =~ /`([^']*)'/ and $1
   end
end

for Ruby >= 1.9 you can uses this:

module Kernel
   private
   def this_method
     __method__
   end
end

[see Stack Over Flow as well]

Check this out, here some lists of good techniques to get started and to impove your Ruby and Rails code:

http://nettuts.com/articles/web-roundups/10-awesome-ruby-on-rails-techniques-to-get-you-started/

http://www.rubyinside.com/19-rails-tricks-most-rails-coders-dont-know-131.html

http://www.rubyinside.com/21-ruby-tricks-902.html

[Awsm picture taken from DesignShark]

class Spaceship < ActiveRecord::Base
  include FlagShihTzu

  has_flags 1 => :warpdrive,
            2 => :shields

end

enterprise = Spaceship.new
enterprise.warpdrive = true
enterprise.shields = false
enterprise.save

enterprise.warpdrive? #=> true
enterprise.shields? # => false

Nice, isn’t it?

Unfortunately named scopes where missing for selecting models easily. So another github fork, another fix, and here were are. Now this works as well:

Spaceship.flagged(:warpdrive).not_flagged(:shields).all

Check it out here: http://github.com/rngtng/flag_shih_tzu/tree/master

Update: replaced ‘routes’ with ‘scopes’ – I’m getting confused with that all the time, how come!?