RVM Ruby Execution with launchctl on osx

This addresses a problem that goes like this:

You want to create a launch file for launchd (launchctl) to run a ruby file periodically or as a daemon.

Various solutions to this problem include creating an RVM alias for the particular ruby version you want to use. Here I present a working version without aliases, just uses the default RVM Ruby. Please not that, for me, the default rvm ruby is 2.2.5.

When you create a sample plist file like this:

<plist version="1.0">
<dict>
<key>Label</key>
<string>com.yourdomain.projectname</string>
<key>ProgramArguments</key>
<array>
  <string>/Users/rahul/.rvm/rubies/ruby-2.2.5/bin/ruby</string> 
<string>test.rb</string>
</array>
<key>KeepAlive</key>
<dict>
<key>SuccessfulExit</key>
<false>
</false></dict>
<key>RunAtLoad</key>
<true>
<key>StartInterval</key>
<integer>21600</integer>
</true></dict> 
</plist> 

The rvm environment does get initialized. You get lots of gem issues.

The trick here lies in not running ruby but:

rvm-shebang-ruby

Simply use:
<plist version="1.0"> <dict> <key>Label</key> <string>com.yourdomain.projectname</string> <key>ProgramArguments</key> <array> <string>/Users/rahul/.rvm/rubies/ruby-2.2.5/bin/rvm-shebang-ruby</string> <string>test.rb</string> </array> <key>KeepAlive</key> <dict> <key>SuccessfulExit</key> <false> </false></dict> <key>RunAtLoad</key> <true> <key>StartInterval</key> <integer>21600</integer> </true></dict> </plist>

Ruby and RVM environments are now correctly updated.

Yeah and you don't need to create any aliases. It will work perfectly fine.