Skip to content

Regrowl GNTP Messages to Other Machines over Network

License

Notifications You must be signed in to change notification settings

snicker/gntp-regrowl

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ReGrowl Server

Forked by snicker in Sept 2013 to act as a headless GNTP server to bouncing messages to other clients. Will eventually support:

  • Forwarding based in incoming messages host address, application name, message type, etc
  • Web GUI for modifying forwarding configuration data

Currently supports:

  • Forwarding all messages to machines as defined in the configuration file
  • Forwarding all messages to Prowl clients with API keys, see example below

Completely based on the work done by KFDM, one of the only GNTP solutions I've seen that works on FreeBSD.

Installing

python setup.py install

Running

$ regrowl -h
Usage: regrowl [options]

Options:
  -h, --help            show this help message and exit
  -a HOST, --address=HOST
                        address to listen on
  -p PORT, --port=PORT  port to listen on
  -P PASSWORD, --password=PASSWORD
                        Network password
  -v, --verbose         

Config File

Regrowl bridges can be controled through a simple config file in ~/.regrowl

This file is also used to configure the destinations for forwarding messages.

[regrowl.server]
port = 12345
password = mypassword

[regrowl.bridge.forward.destinations]
machine1 = network,192.168.1.65,23053,mypassword
iphone1 = prowl,<prowlAPIkey>
examplename = network,<hostname>,<port>,<password>

[regrowl.bridge.local]
enabled = false

[regrowl.bridge.subscribe]
enabled = false

Config file sections are defined by the package name.

See Also

Bitdeli Badge

About

Regrowl GNTP Messages to Other Machines over Network

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 100.0%