Vagrant Notify

Vagrant plugin that redirects `notify-send` from guest to host machine and notifies provisioning status.
Alternatives To Vagrant Notify
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Terraform Provisioner Ansible526
2 years ago22December 06, 202010apache-2.0Go
Ansible with Terraform 0.14.x
Baremetal Operator418322 days ago73September 20, 202226apache-2.0Go
Bare metal host provisioning integration for Kubernetes
Vagrant Notify183
34 months ago16December 24, 2020mitRuby
Vagrant plugin that redirects `notify-send` from guest to host machine and notifies provisioning status.
a year ago1gpl-3.0Groovy
Infrastructor is a server provisioning tool written in Groovy
17 days ago88gpl-3.0Python
:calendar: The infrastructure deployment time machine
Vagrant Guest_ansible64
4 years ago4March 30, 201810mitRuby
Running Ansible in Vagrant Guests
a month ago58May 03, 20222gpl-3.0Ruby
ISO and USB boot disk support for Foreman
Ansible Sshjail55
2 years ago7mitPython
An Ansible connection plugin for provisioning FreeBSD jails remotely
6 years ago1mitShell
Elasticsearch cluster with Docker
Ansible Supervisord36
3 years ago8mitShell
An Ansible role for deploying and configuring Supervisor on unix hosts.
Alternatives To Vagrant Notify
Select To Compare

Alternative Project Comparisons


This project has been archived. Thanks a lot to everyone that contributed with it and used it over the years ❤️‍🔥

If anyone else wants to resurrect it please reach out on Twitter or by other means listed in @fgrehm's website!


Build Status Gem Version

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 notify-send command.

Provisioning notification

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 notifications like:




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| = "ubuntu/trusty64"
  config.notify.enable = false

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| = "ubuntu/trusty64"
  config.notify.bind_ip = ""

WARNING! 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.

By default the local notification server uses the notify_send command in your host PATH for displaying notifications, there is a possibility to use different app without wrapper scripts:

  • notify.sender_app configuration option is used for specifing application name (default: notify-send)
  • notify.sender_params_str defines how params for applications will be passed (default: [--app-name {app_name}] [--urgency {urgency}] [--expire-time {expire_time}] [--icon {icon}] [--category {category}] [--hint {hint}] {message}). You can use these variables (escaped by { and } characters) here:
    • urgency - urgency level for notification
    • expire_time - when notification will expire?
    • app_name - application name
    • icon - icon for the notification (can be multiple, devided by comma)
    • category - category for the notification (can be multiple, devided by comma)
    • hint - icon for the notification (need to use this format: TYPE:NAME:VALUE)
    • message - message to send
  • notify.sender_params_escape - should params will be escaped when passed to script (default: true)

This is example how to to run notifications with build-in MacOS X notifications support:

Vagrant.configure(2) do |config| = "ubuntu/trusty64"
  config.notify.sender_params_str = '-e \'display notification {message} sound name \"default\"\''
  config.notify.sender_app = 'osascript'
  config.notify.sender_params_escape = true

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)


Demo Demo OS X Demo Windows

Known issues

  • 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


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request
Popular Provisioning Projects
Popular Hosts Projects
Popular Configuration Management Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.