Error Sending Notification With Gntp
Contents |
Sign in Pricing Blog Support Search GitHub This repository error sending notification with gntp notify failed Watch 19 Star 981 Fork 215 guard/guard-rspec Code Issues
Error Sending Notification With Gntp Register Failed
13 Pull requests 3 Projects 0 Wiki Pulse Graphs New issue Notifications are terminal-notifier-guard not working through ruby_gntp #88 Closed ghost opened this Issue Jan 2, 2012 · 8 comments Projects None yet Labels None
Growl
yet Milestone No milestone Assignees No one assigned 2 participants ghost commented Jan 2, 2012 I see that the recommended gem to enable Growl notifications is ruby_gntp. I'm just defining these gems in my Gemfile: group :development do gem 'guard' gem 'guard-rspec' gem 'guard-spork' end group :test, :development do gem 'rspec-rails' gem 'spork' gem 'growl' gem 'ruby_gntp' end group :test do gem 'rb-fsevent' gem 'webrat' end I run guard and it gives me the ERROR: Error sending notification with gntp: Connection refused - connect(2): Guard uses GNTP to send notifications. Guard is now watching at '/Users/david/Sites/rails_tutorials/rails_tutorial' Starting Spork for RSpec NOTE: Gem.latest_load_paths is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem.latest_load_paths called from /Users/david/.rvm/gems/ruby-1.9.3-p0/gems/spork-0.8.5/lib/spork.rb:112. NOTE: Gem.all_partials is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem.all_partials called from /Users/david/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems.rb:603. NOTE: Gem.all_partials is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem.all_partials called from /Users/david/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems.rb:603. Using RSpec Loading Spork.prefork block... Spork is ready and listening on 8989! Spork server for RSpec successfully started ERR
Introduction Communication Overview General Message Structure GNTP Information line Header Value Data Types Message Termination Requests REGISTER NOTIFY SUBSCRIBE Generic Headers Connection Handling Custom Headers App-Specific Headers Responses -OK -ERROR Callbacks Socket Callbacks URL Callbacks Forwarding Security Key Generation Encrypting Messages Ports and Discovery Appendix Error Codes Flash Support Websocket Support Examples Introduction The Growl Network Transport Protocol, or GNTP, is a protocol to allow two-way communication between applications and https://github.com/guard/guard-rspec/issues/88 centralized notification systems such as Growl for Mac OS X and to allow two-way communication between two machines running centralized notification systems for notification forwarding purposes. Communication Overview An application MUST first REGISTER with the notification system. This registration will communicate the application's name, the notifications it may send, and details on those http://www.growlforwindows.com/gfw/help/gntp.aspx notifications. Requests to NOTIFY with information not corresponding to a previously registered application/notification pair will be ignored. After REGISTERing, the application may at any time send NOTIFY requests. A NOTIFY request includes the information to be displayed, including title, text, and icon of the notification, and may also include hints to the display server, as detailed below. General Message Structure GNTP messages follow a structured plain text format with lines separated by
notifications using the [ruby_gntp](github.com/snaka/ruby_gntp) gem. This gem is available for OS http://www.rubydoc.info/github/guard/guard/Guard/Notifier/GNTP X, Linux and Windows and sends system https://pythonhosted.org/gntp/ notifications to the following system notification frameworks through the [Growl Network Transport Protocol](www.growlforwindows.com/gfw/help/gntp.aspx): [Growl](growl.info) [Growl for Windows](www.growlforwindows.com) [Growl for Linux](mattn.github.com/growl-for-linux) [Snarl](sites.google.com/site/snarlapp) Examples: Add the `ruby_gntp` gem to your `Gemfile` group error sending :development gem 'ruby_gntp' end Add the `:gntp` notifier to your `Guardfile` notification :gntp Add the `:gntp` notifier with configuration options to your `Guardfile` notification :gntp, sticky: true, host: '192.168.1.5', password: 'secret' Constant Summary DEFAULTS = Default options for the ruby gtnp notifications. { sticky: false } CLIENT_DEFAULTS = Default options for the ruby gtnp client. { host: '127.0.0.1', password: '', port: 23053 } Constants inherited from Base Base::HOSTS Instance Attribute Summary Attributes inherited from Base #options Class Method Summary collapse .available?(opts = {}) ⇒ Boolean .gem_name ⇒ Object .supported_hosts ⇒ Object Instance Method Summary collapse #notify(message, opts = {}) ⇒ Object Shows a system notification. Methods inherited from Base _supported_host?, #images_path, #initialize, name, #name, #normalize_standard_options!, require_gem_safely, title, #title Constructor Details This class inhe
Sending¶ from gntp.notifier import mini # Send a simple growl message with mostly default values mini("Here's a quick message", callback="http://github.com/") gntp.notifier.mini(description, applicationName='PythonMini', noteType='Message', title='Mini Message', applicationIcon=None, hostname='localhost', password=None, port=23053, sticky=False, priority=None, callback=None, notificationIcon=None, identifier=None, notifierFactory=