terminal-notifier is not part of the bundle. Add it to Gemfile. (Gem::LoadError)

[stuffaboutpete]

I'm getting the following error whilst trying to get this workflow set up.

/Applications/Vagrant/embedded/gems/gems/bundler-1.5.3/lib/bundler/rubygems_integration.rb:240:in `block in replace_gem': terminal-notifier is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
from /usr/bin/terminal-notifier:22:in `<main>'

All I've done is install the plugin vagrant plugin install vagrant-notify, created the following script at /usr/local/bin/notify-send (on OSX) and run vagrant up.

#!/bin/bash
terminal-notifier -title "Vagrant Machine" -message "$*"

The machine provisions without issue and then the error appears whenever notify-send is called on the virtual machine. In this case it's a 32bit Ubuntu 13.10 machine.

I can't get get my head around what the error is telling me; it seems like the host vagrant installation doesn't have access to a 'terminal-notifier' command. But I wouldn't know how to fix or get round that.

Any thoughts?

[fgrehm]

Weird.... I'm not a Mac user, so I can't help you much here =/

Why didn't you use grownotify as shown on the readme?

[stuffaboutpete]

Ok, no worries. I only used notification center because it's native and thought it would be simple; it is also mentioned in the readme.

I'll let you know if I get anywhere.

[osrochabr]

+1

[fgrehm]

Something just crossed my mind. Have you tried specifying the full path to the terminal-notifier executable on the /usr/local/bin/notify-send script? Maybe there's some Ruby / Bundler PATH black magic happening and it gets confused about which terminal-notifier it has to run.

[osrochabr]

@fgrehm Actually, i did it, and the error message remain the same. There's some black magic here. When i run /usr/local/bin/notify-send script directly on the host (OS X), this work fine.

[stuffaboutpete]

Yeah same for me, it doesn't make a difference. I've set Growl up now which was very simple :+1:

[fgrehm]

Awesome! I'm working on extracting the notification server out to a separate project and it is likely that it will fix those issues and might make the Mac / Windows integration a bit simpler

[stuffaboutpete]

Ok cool, I'll watch this space.

Cheers for the work, very useful.

[maikelvl]

Any updates on this? Also ran into this. Please share.

[stuffaboutpete]

I've just been using Growl. I'd recommend that route unless you have any specific reason not to...

[maikelvl]

I like native, but for now I use Growl as well. tnx

[fgrehm]

This is what is likely to become the foundation of vagrant-notify 1.0: https://github.com/fgrehm/notify-send-http

I don't own a mac so I'll need some help to try things out over there once I'm able to get a Mac version of the server in place.

[stuffaboutpete]

Sounds interesting. Happy to help, let me know what you need.

[c960657]

Adding unset GEM_PATH RUBYOPT to your wrapper script in /usr/local/bin/notify-send fixes the issue. I don't know enough about Ruby to tell whether this is a fix or a workaround.

[stuffaboutpete]

Makes no difference for me unfortunately.

[c960657]

There are a number of other Ruby-specific environment variables that leak into the script (BUNDLE_BIN_PATH, BUNDLE_APP_CONFIG, BUNDLE_CONFIG, RUBYLIB, BUNDLE_GEMFILE, GEMRC - and possibly others) that may also need to be unset.

[stuffaboutpete]

Excellent, it's now working for me. I had to unset GEM_PATH RUBYOPT and BUNDLE_GEMFILE.

Thank you!

[fgrehm]

Support for Mac OS has just landed into notify-send-http. This will be fixed when this plugin gets updated to use that.

[richardriman]

I have solution for terminal-notifier. I solved it this way:

#!/bin/bash
shift
/usr/local/bin/terminal-notifier -title "Vagrant Machine" -message "$*"

It's because notify-send sends '--' as a first argument and terminal-notifier not understand this syntax.

[alpha01]

Closing. Use https://github.com/fgrehm/vagrant-notify/blob/master/examples/osx/notify-send_terminal-notifier