Page MenuHomePhabricator

Notifications now use WebSockets
Closed, ResolvedPublic

Assigned To
Authored By
epriestley
Jan 8 2015, 6:16 PM
Tokens
"Mountain of Wealth" token, awarded by jayvdb."Love" token, awarded by qgil."Love" token, awarded by richardvanvelzen."Love" token, awarded by avivey."Mountain of Wealth" token, awarded by btrahan.

Description

Notifications have moved from Flash to WebSockets. These are the expected changes for administrators:

  • Upgrading
    • You will need to install the ws module for Node.js. See the documentation below for help.
    • bin/aphlict should no longer be run as root. Run as the user you want to run the server as, instead. This can be any unprivileged user.
    • bin/aphlict might not have permission to write to its PID file or log file now, if you used to run as root. Double check the settings and permissions.
  • Cleanup
    • Port 843 does not need to be accessible anymore, and can be removed from firewall rules.
    • The notifications.user option has been removed. You can delete any configuration you have.
    • The notifications.debug option has been removed. You can delete any configuration you have.
  • Supported Clients
    • Notification support has been removed for IE8 or IE9.
    • Notification support has been added for iPhones (and probably other mobile devices).

You can find details on most of these changes in the documentation, see Notifications User Guide: Setup and Configuration.

You can find technical discussion of this change in T6559.

Event Timeline

epriestley raised the priority of this task from to Normal.
epriestley updated the task description. (Show Details)
epriestley added projects: Notifications, Support.

Wow I just saw notifications on my iPhone

The update went pretty well, and it seems to work just fine!

However, two things I noticed:

  • npm install -g ws is unlikely to work - this normally installs global scripts, but not libraries. You may want to investigate this
  • I got an error about trying to write to /var/tmp/aphlict/pid, which did not exist previously as far as I know. P1699 contains the full trace I got.

Thanks for the awesome update. Now I can spam my co-workers with fancy notifications even more. :3

I got an error about trying to write to /var/tmp/aphlict/pid, which did not exist previously as far as I know. P1699 contains the full trace I got.

It turned out, that Aphilist server now doesn't auto-create folder, where pid file is stored (the /var/tmp/aphlict/pid one). Try creating it and chowning to user who you're running Aphilist under.

epriestley claimed this task.

This has been in production for quite a while.