Websockets - Locally Hosted Alternative for Pusher (Now Free)

JAC

Is there a way to change the colour of new discussion bar?

Thanks

Kyrne

JAC you can via css.

Kyrne

I just wanted to quickly say from the bottom of my heart how much it means to me that you guys all support my development work. It's been a crazy start to my year and it gives me so much joy every time I see one of you subscribing to Websocket (or ReCache)! I'm not going to tag all 15, but you know who you are, thank you!

I can't wait to bring you the latest expansion to the Websocket ecosystem of compatible extensions in the near future.

DursunCan

@Kyrne Can ReCache and this extension be made to work on all platforms? Shared hosting (cPanel, Plesk), virtual servers, web servers (litehttpd, apache, litespeed)

Kyrne

DursunCan WebSocket and ReCache can be made to work on any web server. They can both potentially work on shared hosting depending on the privileges your host gives you. If you only have Plesk or cPanel you are SOL. There's no reason to use ReCache on shared hosting anyway, you're putting your money in the wrong place.

mekici

Kyrne While the Websocket extension is active and there are 1500 people in the forum instantly, the CPU usage is around 50% -60%. When you close the Websocket plugin, this value drops by 20%. Updating 10-15 discussions on the home page starts giving "opps ..." error.

We use 32 CPU dedicated servers in Digitalocean.

askvortsov

mekici For enterprise-grade communities, perhaps it might make sense to include support for pusher alternatives that can be hosted efficiently on a separate process like Poxa? Although it'd be a little bit more complex to set up, a small isolated program written in a websockets-optimized language like Elixir might scale better.

@Kyrne maybe support for that could be included in websockets? I'm hoping to eventually support it in regular Pusher as well, but websockets comes with the benefits of pushing events for private (or generally non-public) discussions.

Kyrne

askvortsov As far as my testing has gone, the websocket server is completely built-in as an option. It should work with any websocket server that uses the pusher protocol without any changes from me.

Kyrne

Paid Add-on Option

For the past 2 days, I've been looking heavily into bundling Poxa into websocket without too much success. Poxa turns out to be quite complicated to build with everything it needs to work with the PHP application let alone get it to work on other OSes. I spent about 8 hours today modifying both the extension and Poxa trying to get them to work in tandem. While eventually did get it to work, I've come to the conclusion that it will be much too complicated to distribute due to cross-platform issues and the overall complexity and time requirement of setup.

However, Poxa runs SIGNIFICANTLY faster and more efficiently than the built-in PHP websocket server (elixir & erlang are both built for this purpose). I want you all to be able to take advantage of this performance especially when there are users like @mekici who have really large forums that can really benefit from this. That is why I am offering a paid upgrade service to build and install a custom version of Poxa specifically for your forum.

This is not something that every community needs, for most forums, the built-in server works just fine, if you aren't noticing significant hits to resource usage because of websocket, don't bother with this. For those of you who do need the extra performance, contact me on discord: Kyrne#9728 and we can set up a time for me to do this and discuss. I will be charging $40 for this service, it should take about an hour to complete, requires no work on your end, and will not need any extra maintenance in the future.

Kyrne

Well, do I have some news for you all.

I spent all Saturday and a good portion of today modifying the Erlang/Elixir coding languages themselves to disable some OpenSSL hooks that were preventing the cross-platform function of the Poxa server. I'm happy to report that I was successful and after many half-hour compilation waits and @askvortsov's incredible and tireless help with testing I have a beta version of the new server ready to go - free of charge.

2.4.0

(beta) Integrated Poxa - a high-performance websocket server written in Erlang and Elixir - Should run at least 3x as efficiently.
- No configuration necessary, just stop your current websocket server and run the new one.
- You can run the new server with php flarum websocket:beta (instead of serve)
- Linux/MacOS Only!

If you run into any issues, please report them! The old server is still available if you run into trouble.

Fun fact: this is the first functionally cross-language Flarum extension!

Fantomen

Kyrne Appears to be requiring GLIBC 2.29? As I´m running Debian 10 the latest stable package appear to be 2.28-10.

ram0ng1

Kyrne php flarum websocket:beta

I get the error:

/home/admin/domains/domain.com.br/public_html/vendor/kyrne/websocket/poxa-Linux/erts-10.3.5.15/bin/beam.smp: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

Use CentOS..

how to proceed?

Kyrne

Fantomen let me see if I can compile it for lower versions

Kyrne

Fantomen

2.4.1

Reduce Glibc minimum requirement for Poxa - 2.27
- Should now work with Ubuntu 18.04+, RHEL 8+, Fedora 28+, Debian 10+
- You might need to install new curses 5. If you get an error about "loading shared libraries" run sudo apt install libncurses5
Shaved a tiny bit off the total package size

Fantomen

Kyrne That would be great!

Fantomen

Kyrne

Thank you for the update. I still have a few issues though.

After I start the websocket I receive this message. It doesn´t really appear to start though;

Warning: This implementation of the websocket server is in beta, you may encounter errors.
Attempting to start Poxa - this may take a few seconds...

09:26:25.039 [info]  Starting Poxa via kyrne/websocket, app_id: 681

09:26:25.039 [info]  Starting without SSL on port 2083

Console gives following error:

pusher.min.js?_=1612863453959:8 Pusher :  : ["State changed","initialized -> connecting"]
pusher.min.js?_=1612863453959:8 Pusher :  : ["Connecting",{"transport":"ws","url":"wss://hockeybulletin.se:443/app/k3sUVaB0pqRPlSnwMrLtEuNkiyURUH6I?protocol=7&client=js&version=5.1.1&flash=false"}]
pusher.min.js?_=1612863453959:8 WebSocket connection to 'wss://hockeybulletin.se/app/k3sUVaB0pqRPlSnwMrLtEuNkiyURUH6I?protocol=7&client=js&version=5.1.1&flash=false' failed: Error during WebSocket handshake: Unexpected response code: 400
createWebSocket @ pusher.min.js?_=1612863453959:8
pusher.min.js?_=1612863453959:8 Pusher :  : ["State changed","connecting -> unavailable"]
pusher.min.js?_=1612863453959:8 Pusher :  : ["Connecting",{"transport":"ws","url":"wss://hockeybulletin.se:443/app/k3sUVaB0pqRPlSnwMrLtEuNkiyURUH6I?protocol=7&client=js&version=5.1.1&flash=false"}]
pusher.min.js?_=1612863453959:8 WebSocket connection to 'wss://hockeybulletin.se/app/k3sUVaB0pqRPlSnwMrLtEuNkiyURUH6I?protocol=7&client=js&version=5.1.1&flash=false' failed: Error during WebSocket handshake: Unexpected response code: 400

Kyrne

Fantomen

We fixed this over Discord, turns out there's a typo in the Nginx config I gave you guys.

There's a duplicate set header line:

	location @ws {
	    proxy_pass             http://127.0.0.1:2083;
	    proxy_set_header Host $host; <--- THIS LINE
	    proxy_read_timeout     60;
	    proxy_connect_timeout  60;
	    proxy_redirect         off;

	    # Allow the use of websockets
	    proxy_http_version 1.1;
	    proxy_set_header Upgrade $http_upgrade;
	    proxy_set_header Connection 'upgrade';
	    proxy_set_header Host $host;
	    proxy_cache_bypass $http_upgrade;
	}

Please remove this line, it prevents the new beta websocket server from running. It will not break anything since it's a duplicate.

2.4.2

Cleanup some Poxa backend code for security purposes

matteocontrini

Hi, bug report 🙂 when clicking the yellow banner in the side pane the panel disappears for a moment.

Here's a video:

EDIT: also, it appears that after doing this the side panel doesn't stay open, when you move the mouse away from the top left icon it closes

Ffuser1

matteocontrini clicking it reloads the content bringing the updated discussion up. It's normal behavior.

matteocontrini

Ffuser1 in fact I said that the panel disappears for a moment, which is definitely not the normal behaviour and it didn't work like this in previous versions 😉

Kulga

I've been looking into adding this since it was released and I finally had the chance to do it, so thank you! This plugin is great

With Auto Update Discussions enabled, I'm getting this bug when creating a new discussion, it comes up as [Deleted]
Refreshing anything causes the correct value to show up.
I'm using version 2.4.2

deleted showing up after creating new post

« Previous Page Next Page »