terminal-notifier is not part of the bundle. Add it to Gemfile. (Gem::LoadError) about vagrant-notify HOT 20 CLOSED

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?

from vagrant-notify.

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.

from vagrant-notify.

+1

from vagrant-notify.

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.

from vagrant-notify.

@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.

from vagrant-notify.

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

from vagrant-notify.

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

from vagrant-notify.

Ok cool, I'll watch this space.

Cheers for the work, very useful.

from vagrant-notify.

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

from vagrant-notify.

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

from vagrant-notify.

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

from vagrant-notify.

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.

from vagrant-notify.

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

from vagrant-notify.

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.

from vagrant-notify.

Makes no difference for me unfortunately.

from vagrant-notify.

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.

from vagrant-notify.

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

Thank you!

from vagrant-notify.

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

from vagrant-notify.

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.

from vagrant-notify.

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

from vagrant-notify.