rails runner… with a relative path

Well, you know what ./script/runner is?

If so, you’ll know you can’t use it to build script without using an absolute path in the shebang line in your custom scripts:

> ./script/runner -h
Usage: ./script/runner [options] ('Some.ruby(code)' or a filename)
You can also use runner as a shebang line for your scripts like this:
#!/usr/bin/env /path/to/your/app/script/runner
...

 So here’s the solution! (here the script is saved in the script dir)

#!/usr/bin/env ruby
unless $0 =~ /runner/
  exec("#{File.dirname(__FILE__)}/runner #{__FILE__}")
  # "exec" exits the current processing, so this comment won't reached (thanks to Arthaey Angosii)
end
# Your great script goes here!

 Alternative:

#!/usr/bin/env ruby
$: << File.dirname(__FILE__)
ARGV[0] = __FILE__
load 'runner'
#your code here

Possibly related posts: (automatically generated)

Published in: on January 23, 2008 at 10:43 am Comments (4)

The URI to TrackBack this entry is: http://elia.wordpress.com/2008/01/23/rails-runner-with-a-relative-path/trackback/

RSS feed for comments on this post.

4 Comments Leave a comment.

  1. On October 25, 2008 at 7:38 pm Arthaey Angosii Said:

    If you use exec() instead of backticks, STDOUT will continue to work. Otherwise, the backticks will swallow any writes to STDOUT by the rest of the script.

    Reply
  2. On October 27, 2008 at 9:51 am ~Elia Said:

    You’re right, thanks for the suggestion! :)

    Reply
  3. On December 4, 2008 at 5:31 pm Andrej Said:

    your alternative solution runs code twice ;)

    Reply
  4. On December 4, 2008 at 6:11 pm Andrej Said:

    This one works, uses default environment. If you want to override the environment, set ENV(’RAILS_ENV’)

    ——–
    #!/usr/bin/env ruby
    require File.dirname(__FILE__) + ‘/../config/boot’
    require RAILS_ROOT + ‘/config/environment’

    puts “Running in environment #{RAILS_ENV}…”

    (your code goes here)

    Reply

Leave a Comment