3.0.0

Presence Channels

• Websocket now features a presence channel that is automatically subscribed to when viewing individual discussions (logged in users only!)
  • Typing indicators for those replying to discussions at the bottom
  • Shows users that are currently viewing a discussion on the side bar
  • Easy extending (see dev guide below)

Statistics (beta)

• See how things are going with your websocket server
  • Peak connection and websocket message counters now on the dashboard of your admin page
  • Configurable interval for statistics to cater to your forum's traffic
  • Stats are automatically deleted after 10 days
  • There will be a blank box on your dashboard until you have your first statistic

Notes

• The api changed a bit in this release, if you hook into websocket, take a look at the guide below
• Statistics are only enabled for the non-Poxa server. While I didn't find any performance difference with stats on vs off, this is to keep Poxa as the most high-performance option
• The chart may need to be tweaked in the future depending on feedback. If you can't see some data, or the scale is wrong, feel free to reach out to me

Installing

1. Shutdown your running websocket server
2. Update the plugin composer update kyrne/websocket
3. Run the migrations php flarum migrate
4. Clear your cache php flarum cache:clear as well as any Cloudflare or other server caches
5. Configure the stats interval on the websocket admin page
6. Start the websocket server once again
7. Wait for the first interval to pass and check the graph!

Dev Notes

• You now have a dedicated way to access the pusher instance. Simply resolve the app.pusher promise and you will find the pusher instance directly on the returned value's .pusher key
• Channels can now be found under that same value's .channel key
• The presence channel can be accessed via app.discussions.presence, it is automatically updated with the discussion that the user is currently viewing (don't forget to bind to an event each time a new discussion is viewed!)

mekici I did, there's no good space to put it right now. I'll look into another place to put it, maybe under or on top of the mobile slider. For the future though.

Typing indicator still works.

HD3D Apache will not have any effect on the setup of the websocket server using my methods. You will only need to utilize the nginx portion. Check the GitHub page for detailed instructions on how to set that up.

If you want to use Apache for it I cannot provide support, I've never attempted it and it doesn't seem like the best method to me as Apache wasn't built with proxy-ing in mind.