Installed the extension, I see no realtime updates

luceos

matteocontrini ah that error is caused by missing fof/follow-tags, I patched it already just need to tag a version.

matteocontrini

luceos Maybe a flag on the config that says daemon-running-locally or perhaps even inside the daemon so that it writes the defaults to the database?

Would the concept of presets make sense?

The default configuration right now is ok only if you can expose port 6001 on the public IP, but I don't expect setups similar to mine to be uncommon.

Or more simply: the documentation could just provide configuration examples for different setups so that you know what to set based on your setup. The config.php file needs to be modified anyway, so...

luceos

Presets make a lot of sense, that's also why one is already hardcoded for Blomstra 😉 I just need to figure out what makes sense for most users and yours, really, doesn't seem too uncommon.

I think the biggest hurdle for most is setting up the proxy. As you need to think about the daemon configuration and proxy configuration thereafter, things get quite complicated.

I'll do my best to update the documentation in the coming days and include a preset or two.

matteocontrini

luceos great.

When can I expect the new version to have the issue above fixed? 😇

luceos

matteocontrini I tagged 0.2.5-beta.5, it fixes the follow tags issue. Haven't been able to release everything I have been working on yet.

matteocontrini

luceos thanks!

Is the following command the right way to upgrade? I couldn't do it in other ways, it otherwise said nothing to update...

composer require blomstra/realtime:"0.2.5-beta.5@beta"

However after updating I see no WebSocket connections being created by the clients at all. I see no WS in the network tab of the browser, and no errors in the console. I've cleared the cache and tried with multiple browsers. I might be doing something wrong but I don't think I changed anything else.

luceos

matteocontrini

composer require blomstra/realtime:"*@beta"

Should suffice.

matteocontrini

luceos if I run it now it goes back to 0.2.4

$ composer require blomstra/realtime:"*@beta"
./composer.json has been updated
Running composer update blomstra/realtime
Loading composer repositories with package information                                        Updating dependencies
Lock file operations: 0 installs, 1 update, 0 removals
  - Downgrading blomstra/realtime (0.2.5-beta.5 => 0.2.4)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
  - Downgrading blomstra/realtime (0.2.5-beta.5 => 0.2.4): Extracting archive
Generating autoload files
104 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

luceos

matteocontrini ah prefer stable is on 🙂

composer require blomstra/realtime:"0.2.5@beta"

matteocontrini

luceos now:

$ composer require blomstra/realtime:"0.2.5@beta"


  [InvalidArgumentException]
  Could not find package blomstra/realtime in a version matching "0.2.5@beta" and a stability matching "dev".

I guess it's "0.2.5-beta.5@beta" as mentioned above?

And if I go back to that version, hoping it's the right one, I see the issue mentioned above, i.e. no WS connections being created 🤔

Thanks for the patience.

luceos

matteocontrini the fixed constraint would be:

composer require blomstra/realtime:"0.2.5-beta.6"

But a minimum one should also work:

composer require blomstra/realtime:">= 0.2.5-beta.6"

Let me know if that works, sorry about all this.

matteocontrini

luceos the first one works, the second one doesn't, for the record (Root composer.json requires blomstra/realtime >= 0.2.5-beta.6, found blomstra/realtime[0.2.5-beta.6] but it does not match your minimum-stability.).

Anyway, now I'm on 0.2.5-beta.6 and the admin dashboard confirms that, I cleared the cache, but I still see no WS being created.

You can check yourself here: https://forum.fibra.click/

It appears that when it worked I was on 0.2.4, not 0.2.5-beta.x 🤔

Thank you.

luceos

matteocontrini okay that was stupid; try 0.2.5-beta.7; sorry about that.

matteocontrini

luceos is it published already? It says:

Could not find package blomstra/realtime in a version matching "0.2.5-beta.7" and a stability matching "dev".

P.S. https://extiverse.com/premium/subscriptions is returning "500 | server error" to me

luceos

matteocontrini it is now. Took extiverse a bit to catch up 😉

matteocontrini

luceos ah great. Updated successfully, but I still see this error:

luceos

matteocontrini tagged 0.2.5-beta.8; I have tried to test all scenario's but the code should now work with all of them 😉 More integrations with other extension means more complexity.

matteocontrini

luceos it works, thanks!

I'll report if I notice anything strange.

In the meantime, is there a way to reduce logging of the extension? In 6 hours I already have 1 GB of debug-level logs in my log file.

EDIT: not sure if it's normal but for every new post it seems to deliver the new post event to "private-user-*" channels in a loop, and it takes too much time... My CPU is constantly at 40% with 4 vCPUs... Jobs are being delayed and realtime features aren't really realtime in this way.

matteocontrini

I'm afraid I had to disable the extension. It's sending 15.000 individual events for each new (public) post, and notifications and other jobs are getting delayed.

luceos

matteocontrini EDIT: not sure if it's normal but for every new post it seems to deliver the new post event to "private-user-*" channels in a loop, and it takes too much time... My CPU is constantly at 40% with 4 vCPUs... Jobs are being delayed and realtime features aren't really realtime in this way.

You are using the queue right? Redis?

matteocontrini

luceos yes, exactly, forgot to mention that.