danielunited If you're talking about pressing the button to reload the discussion list on new posts - yeah, that's still there.
Websockets - Locally Hosted Alternative for Pusher (Now Free)
I hope this extension will be converted to free in the near future
I think Kyrene apply crowd-funding for make it free to use. May be he collect 2000-3000 dollars to make open source extension.
ram0ng1 I am saving money to buy annual plan my forum is not big
1 Dollar = 6,85 Turkish Liras and bread price in Istanbul 1.5 lira.
1.0.6
- Added custom page
Since we have huge problems to get Pusher running on our provider space, I wonder if we could test to get websockets running. If so, we would be interested in the "once" plan. Is there a possibility to get a test license and try to get it working before purchasing it?
fakruzaruret You need to update that pic.
1.0.7
- Added a backend log output when debug mode is on. To help me debug any problems you guys may have.
- Edited
1.0.8
- Beta 14 support
Big thanks to @askvortsov for updating this while I'm at school!
Lovely. Thank you!
- Edited
How to get it installed?
me@my-host:~/domains/dev.flarum.local/flarum$ composer require kyrne/websocket
Using version ^1.0 for kyrne/websocket
./composer.json has been updated
Running composer update kyrne/websocket
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- kyrne/websocket[1.0, ..., 1.0.7] require beyondcode/laravel-websockets 1.3 -> satisfiable by beyondcode/laravel-websockets[1.3.0].
- beyondcode/laravel-websockets 1.3.0 requires pusher/pusher-php-server ~3.0 || ~4.0 -> found pusher/pusher-php-server[3.0.0, ..., v3.4.1, v4.0.0, ..., v4.1.4] but the package is fixed to 2.6.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires kyrne/websocket ^1.0 -> satisfiable by kyrne/websocket[1.0, ..., 1.0.7].
Use the option --with-all-dependencies to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You are using a snapshot build of Composer 2, which may be the cause of the problem. Run `composer self-update --stable` and then try again. In case it solves the problem, please report an issue mentioning Composer 2.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I've tried also:
$ composer require kyrne/websocket 1.0.8
$ composer require kyrne/websocket 1.0.8-beta.1
$ composer require kyrne/websocket 1.0.8-beta.14
$ composer require kyrne/websocket:1.0.8
$ composer require kyrne/websocket:dev-master
No luck and extiverse reporting it as incompatible
https://extiverse.com/extension/kyrne/websocket
No luck
It's only start complaining about oauth:
$ composer require kyrne/websocket --with-all-dependencies
Using version ^1.0 for kyrne/websocket
./composer.json has been updated
Running composer update kyrne/websocket --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- league/oauth2-facebook 2.0.3 requires league/oauth2-client ^2.0 -> found league/oauth2-client[2.0.0, ..., 2.5.0] but it conflicts with another require.
- fof/oauth 0.1.0 requires league/oauth2-facebook ^2.0.3 -> satisfiable by league/oauth2-facebook[2.0.3].
- fof/oauth is locked to version 0.1.0 and an update of this package was not requested.
Use the option --with-all-dependencies to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You are using a snapshot build of Composer 2, which may be the cause of the problem. Run `composer self-update --stable` and then try again. In case it solves the problem, please report an issue mentioning Composer 2.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
A quick little update: I'm still waiting on a few things to get Websocket working on beta 14.
I also recently discovered a memory leak with the help of a few users, I'll get this patched up and included in the beta 14 version. Also on the roadmap for the future is a statistics widget for the admin portal, no eta on that though.
- Edited
2.0.0
- Actual compatbility with beta 14 (14.1 is required)
- Fix for memory/cpu usage leak
- Increased time between pings to the server, actually closes the connection if that ping is not responded to
- Added option to only allow connecting to the websocket server if the user is logged in
- Some changes were made to allow for statistics logging in the future
- Changes made to ensure each user only has 1 connection to the server (even across browser tabs), further reducing cpu/memory overhead
- Defer loading pusher script to improve page load time
- So many under the hood changes to make it better, more reliable, and more scalable - it's basically an entirely new extension code wise.
Make sure to turn off the websocket server before updating then restart it after.
Looks like still not available:
$ composer require kyrne/websocket
Using version ^1.0 for kyrne/websocket
./composer.json has been updated
Running composer update kyrne/websocket
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- kyrne/websocket[1.0, ..., 1.0.7] require beyondcode/laravel-websockets 1.3 -> satisfiable by beyondcode/laravel-websockets[1.3.0].
- beyondcode/laravel-websockets 1.3.0 requires pusher/pusher-php-server ~3.0 || ~4.0 -> found pusher/pusher-php-server[3.0.0, ..., v3.4.1, v4.0.0, ..., v4.1.4] but the package is fixed to 2.6.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires kyrne/websocket ^1.0 -> satisfiable by kyrne/websocket[1.0, ..., 1.0.7].
Use the option --with-all-dependencies to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You are using a snapshot build of Composer 2, which may be the cause of the problem. Run `composer self-update --stable` and then try again. In case it solves the problem, please report an issue mentioning Composer 2.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
$ php flarum info | grep 'Flarum core'
Flarum core 0.1.0-beta.14.1