A Vagrant plugin that forwards
notify-send from guest to host machine and
notifies provisioning status. See it in action
Make sure you have Vagrant 1.4+ around and run:
$ vagrant plugin install vagrant-notify
notify-send from guest VMs
Whenever you run
vagrant up, a Ruby TCPServer
will fire up on a port within the usable port range
and a Ruby script
will be copied over to the guest machine to replace the original
Apart from redirecting
notify-send from the guest VM to the host, whenever
a Vagrant 1.4+ provisioner starts or completes running you'll also receive
Since Linux distributions have
notify-send pre-installed, everything should work out of the box.
Check out our OS X notify-send compatible scripts.
Check out our Windows notify-send compatible scripts.
Notification server is enabled by default on all guests. You can individually disable the plugin by adding a false boolean to the notify.enable option in your
Vagrantfile configuration block
Vagrant.configure(2) do |config| config.vm.box = "ubuntu/trusty64" config.notify.enable = false end
Please note that as of v0.5.1, the notification server will automatically be disabled for any of the following cloud providers.
By default, the notification server is binded to local interfaces. For networking different than your provider's default network configuration, you can use the notify.bind_ip configuration option to bind the notification server onto a different local ip address.
Vagrant.configure(2) do |config| config.vm.box = "ubuntu/trusty64" config.notify.bind_ip = "18.104.22.168" end
Do NOT bind the notification server to an IP accessible over a network! The notification server does not have any authentication and doing so will leave your system vulnerable to remote command execution.
Providers and Guests
vagrant-notify supports the following providers:
vagrant-notify has been tested and known to work with Linux, Solaris 11, FreeBSD, OpenBSD, and NetBSD guests. (notify-send icon forwarding feature is not supported on BSD guests)
- On rare occasions the notification server may stop receiving notifications if the host is suspended/hibernates. The notification server may need to be manually restarted if that's the case.
vagrant notify --restart
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request