Realtime - self hosted websocket for instant updates

matteocontrini

@IanM thanks for the updates! Since you're working on the extension, do you have an idea of what might be causing this issue I reported on the Blomstra Community? https://blomstra.community/d/213-queue-jobs-duration-for-realtime

It's stopping me from using the extension unfortunately...

Thanks.

IanM

matteocontrini I remember I did also look at this a while back, but I was also unable to replicate the problem. Which queue driver are you using?

matteocontrini

IanM I'm using Redis (blomstra/flarum-redis)

GreXXL

matteocontrini I think this is not necessarily linked to the queue driver. I have seen delays as well since getting this to run and I am just using the DB queue.

IanM

matteocontrini I need to understand a little more about your setup/configuration here, please

I assume you have your web process, queue worker and realtime process all running within the same VM/server/node/etc?

One config value that can really have an impact is the php-client-host. When everything is running with the same environment, this will benefit from being seto to localhost, rather than having to loopback on itself

matteocontrini

GreXXL that's my impression too, since the logs show that the delay is between the start and the end of the processing

matteocontrini

IanM I assume you have your web process, queue worker and realtime process all running within the same VM/server/node/etc?

Yes

IanM One config value that can really have an impact is the php-client-host. When everything is running with the same environment, this will benefit from being seto to localhost, rather than having to loopback on itself

It is set to localhost, here's the configuration:

'websocket' => array(
        'js-client-host' => 'wss.fibra.click',
        'js-client-port' => 443,
        'js-client-secure' => true,
        'php-client-host' => 'localhost',
        'php-client-port' => 6001,
        'php-client-secure' => false,
  )

From what I remember everything works well for a while but after about an hour after enabling the extension each job starts to take seconds. Other jobs (unrelated to realtime) keep working the same way (no delays).

IanM

0.2.14

🩹 🐛

fix an issue introduced in 0.2.12 which prevented non-admin users with view who types permission from seeing the typing indicator

IanM

0.2.15

✨ Typing indicator improvements

Users now have the choice of displaying x users are typing, or username is typing
Username option respects Show online status privacy setting
Animated typing icon (requires FontAwesome 6), otherwise is static. Animation also respects the prefers reduced motion browser/OS preference.

firefox_J5RBI5LdBe

🔮 In future

I intend to relocate the typing indicator to the end of the post stream, but do do this in a sensible and extensible way, a minor core change will be required. Watch this space.

⬆️ Updating

composer update blomstra/realtime
php flarum cache:clear

Yiju

I've purchased the extension.
Question Showing "no pusher/websocket" after enabling debug mode.
More info
Server status:

Starting websocket server, which listens on 0.0.0.0:6001.
App key expected is 40d6928422bb0aeb98784bfefc15d69d
App secret expected is a891c51a9322898185be260b84c99d66
Max connections 1000

Then just nothing seems to work?

CyberGene

Can I install this on an external server, e.g. on a DigitalOcean droplet and use it from a Flarum instance on shared hosting (SiteGround)?

luceos

CyberGene yes, but right now the daemon acts as part of an extension. This means you need to deploy the same code, connect to the same database and hook into the same queue.

At Blomstra we run the daemon similar to the queue, inside the same pool as a dedicated vm so to say.

luceos

0.2.18 adds the ability to restart the daemon.

By default it will now restart whenever an extension is enabled or disabled. This prevents any errors from keeping the daemon in an old state.

There's now also a new command realtime:halt to signal to the daemon to stop, your demonizing script should then auto restart it. This command is helpful after updating the Flarum installation or in a CI/CD pipeline.

Full details: https://extiverse.com/extension/blomstra/realtime

kebindong

Hi, I just bought the realtime for testing.

but when I enable it , it shows This extension has no settings.

As I know there are some setting, because I first trying to install and enable realtime in my alt site, and it works.

But in my main site, I did the same thing, it shows this extension has no settings when I enabled realtime.

My alt site use the php7.4. my main site is php8.2.

So, May I ask if the real time support php 8.2?

thank you

luceos

kebindong but when I enable it , it shows This extension has no settings.

try clearing the cache from the admin area

kebindong

Hi, I configued websocket

'websocket' => [
      'server-port' => 6001,
      'js-client-port' => 443,
      'php-client-host' => '127.0.0.1',
      'php-client-port' => 6001,
      'php-client-secure' => false,
  ]

php flarum queue:work
Output:

[2023-03-03 11:13:07][UrPMn047nbRnAX5MUkfcwtjkhQJ5raiK] Processing: Blomstra\Realtime\Push\Jobs\SendTriggerJob
[2023-03-03 11:13:07][UrPMn047nbRnAX5MUkfcwtjkhQJ5raiK] Processed: Blomstra\Realtime\Push\Jobs\SendTriggerJob

But, the new discussions / replies won’t push to discussion list. I still have to refresh page to see new discussions..

May I ask how to fix it?

thanks

luceos

kebindong do you see any errors in your browser console?

kebindong

luceos just checked the browser console in chrome

WTFc72Dx23zwEWKxxK30L7xUOJQ.js:103 WebSocket connection to 'wss://www.sugarasian.org/app/bc995910d0f997d2d6f79a73a40e19b0?protocol=7&client=js&version=7.4.0&flash=false' failed: 
RequestIntercept.window.WebSocket @ WTFc72Dx23zwEWKxxK30L7xUOJQ.js:103
createWebSocket @ forum.js?v=ffd47433:461
getSocket @ forum.js?v=ffd47433:461
e.connect @ forum.js?v=ffd47433:461
t @ forum.js?v=ffd47433:461
t.emit @ forum.js?v=ffd47433:461
e.changeState @ forum.js?v=ffd47433:461
transportConnectionInitializer @ forum.js?v=ffd47433:461
t.connect @ forum.js?v=ffd47433:461
t.tryStrategy @ forum.js?v=ffd47433:461
c @ forum.js?v=ffd47433:461
(anonymous) @ forum.js?v=ffd47433:461
(anonymous) @ forum.js?v=ffd47433:461
(anonymous) @ forum.js?v=ffd47433:461
WTFc72Dx23zwEWKxxK30L7xUOJQ.js:103 WebSocket connection to 'wss://www.sugarasian.org/app/bc995910d0f997d2d6f79a73a40e19b0?protocol=7&client=js&version=7.4.0&flash=false' failed: 
RequestIntercept.window.WebSocket @ WTFc72Dx23zwEWKxxK30L7xUOJQ.js:103
createWebSocket @ forum.js?v=ffd47433:461
getSocket @ forum.js?v=ffd47433:461
e.connect @ forum.js?v=ffd47433:461
t @ forum.js?v=ffd47433:461
t.emit @ forum.js?v=ffd47433:461
e.changeState @ forum.js?v=ffd47433:461
transportConnectionInitializer @ forum.js?v=ffd47433:461
t.connect @ forum.js?v=ffd47433:461
t.tryStrategy @ forum.js?v=ffd47433:461
c @ forum.js?v=ffd47433:461
(anonymous) @ forum.js?v=ffd47433:461
(anonymous) @ forum.js?v=ffd47433:461
(anonymous) @ forum.js?v=ffd47433:461
WTFc72Dx23zwEWKxxK30L7xUOJQ.js:103 WebSocket connection to 'wss://www.sugarasian.org/app/bc995910d0f997d2d6f79a73a40e19b0?protocol=7&client=js&version=7.4.0&flash=false' failed:

It shows failed in console, may I ask what problem is that?
thank you

mekici

after the last laugh the websocket stopped working. There is the following error in the browser console.

runtime.ts:115 WebSocket connection to 'wss://flarumtr.com/app/5da45286ef237668a35a87e8d5575602?protocol=7&client=js&version=7.4.0&flash=false' failed:

luceos

mekici is the daemon running? Nothing changed much in the last few versions.

mekici

luceos Last time I installed it with you, I updated twice and there was no problem.

realtime RUNNING pid 3806075, uptime 0:00:19

The supervisor seems to be doing his job. I tried different ports (2053, 2083, 8443) but it didn't work

« Previous Page Next Page »