1. Growl prefs.
2. Install
3. Growl.pl settings
4. Growl-net settings
5. Reload

Growl-net documentation

1. Firstly, you need to setup Growl correctly on the computer you’ll be recieving the growls. (Usually the one you ssh from)

2. You’ll need to have both the first options set, and Net::Growl needs a password, so set something simple. After these have been set, you’ll need to restart Growl before it’ll work. Next you’ll need to install the script. Put it in the ~/.irssi/scripts dir of the user which you log in as on the remote machine. If you like, you can also link it to ~/.irssi/scripts/autorun by usingln ~/.irssi/scripts/growl-net.pl ~/.irssi/scripts/autorun/growl-net.pl. Next, load the script with ‘/script load [autorun/]growl-net’ . You should see some output like: -!- Irssi: >> growl-net 0.01 loaded (/growl-net for help)

19:11 -!- Irssi: >> growl-net 0.03b1 loaded (/growl-net for help. /gn-test to test.)
19:11 -!- Irssi: Loaded script growl_net

1. Next you’ll need to set Growl-net’s variables. Since this script was based on the original growl.pl script that came with Growl, I have used some of it’s variables. This means that you can set the behaviour of both scripts, if you use irssi both locally and remotely on the same machine, you can get growl’s when you want. The settings are growl_show_privmsg, growl_show_hilight and growl_show_notify. They will let you decide if you want growls on private messages, hilights and notify’s respectively. These are all boolean values, so they’re either ON or OFF (Use /set growl_show_privmsg OFF to surn off growls for PM’s).

2. Now you’ll need to set the growl_net_* settings. These are growl_net_pass, growl_net_client and growl_net_server. growl_net_pass is the password you have set on your local machine above.

   growl_net_client is the address to your local machine. If Irssi is running on your local machine, that can be left as ‘localhost’. If irssi is running remotely on another Mac, then you can use it’s Bonjour name, found under sharing prefs in system prefs. It will be the name shown there, with .local added to the end. (G5.local in this case).

   • If irssi is running on a non Mac, you’ll have to either use the IP address of the machine, or a hostname that the remote machine can be accesses with.
   • If you want to use this over the internet, there are a few options. First one is to just go to whatismyip.org and enter that as your growl_net_client. This will probably work fine if you have a static IP address, but for dynamic addresses, it’s a bit more tricky. I would suggest using a service like DynDNS.com, and giving your home computer a real hostname (It’s what I use for this site, hence the homeip.net). This is beyond the scope of these instructions, but it’s easily found on Google. You’ll also need to set up port forwarding on your router:

   • For Airport:

     1. Open Airport Admin utility, /Applications/Utilities/AirPort Admin Utility.app
     2. Select your router, and and click Configure. [enter password as necessary]
     3. Go to the port mapping tab.
     4. Click add.
     5. Hopefully, your airport usually assigns the same IP to your computer when you connect to it each time you connect to it, like mine does (Usually). For the public port, put 9887, for the Private address, put in the last digit of your local IP address [figure that one out yaself], and port 9887 for the private port.
     6. press OK, click Update, wait a bit, then everything should be fine.
     7. If this doesn’t work, Google it, because this is just what works for me

   • growlnetserver is a name that you can give your remote host. It’s only used for registration with Growl. I have irssi running on our OpenBSD router, so I set this to OpenBSD. When the script registers with Growl, it says ‘irssi OpenBSD registered’, useful if you use more than one host. To keep this blank, use /set growlnetserver (That’s growlnetserver with two spaces after it)

   • growlnetsticky Set this to ON if you want growls to be sticky, so they’ll stick around if you’re not there to see them.
   • growlnetstickyaway Set this to ON to have growls made sticky when you’re Away.

3. Now reload the script with /script load growl-net, and hopefully you should see the script register with Growl on your local machine. If not, make sure the settings are correct: growlnetclient should be the machine you are at, and growlnet_server should be the machine irssi is running on. Also make sure the password is correct.