Hey Chris, yes, trying to get WebSockets turned on. Thanks for looking.
Hi,
So the WebSocket support has been updated. The easiest way to get it, is to do a fresh install. If that’s not possible, then I can write out a patch.
The examples and docs have been updated as well. A fresh install includes the “echo” example by default, but you still need to enable WebSockets.
Now, for whatever reason, you need to run the command twice. I’ll take a look at it soon. So log in as coronium user and run:
sudo coronium-tools wson
sudo coronium-tools wson (for good measure <_< )
sudo service coronium reload
Follow the rest of the documentation and you should be able to connect. You can use can just drop the “ws.html” into your browser window for testing.
Let me know how it goes.
Cheers.
I have a bunch of data on the installation I’m currently using (DigitalOcean). For the Coronium scripts, I could just replace them on a fresh install with my local copies, but if I do a fresh install is there a way to transfer over all the other database data and uploaded files etc?
Hi,
What response do you get if you enter this on your instance?
which coronium-tools
LMK
it says, /usr/local/bin/coronium-tools
Hi,
Ok, lets recap:
-
You log in with coronium user
-
You issue a sudo coronium-tools wson
2a. You may be prompted for your password
2b. You enter password
-
You should get no result. That means no error. Doesnt mean it worked obviously.
-
You issue a sudo service coronium reload
At that point you should be able to use the WebSocket. You can try issuing the sudo coronium-tools wson again (for good measure).
Success! Thank you!