[FEAT] Disable websocket from console

Is it a way to disable websocket from console ? I remove service from docker-compose but it's instanciate on console whatever page I'm on (to know realtime connections stats I thinks ?)

Hey

seems like it isnt possible as of now, but would make a cool feature request

https://github.com/appwrite/appwrite/issues/5679 🙂

[FEAT] Disable websocket from console

why did you disable it from docker-compose?

Cause I don't need it

but the console does 😜 does the realtime container really use that much resources?

Use for stats on dashboard only no ?

Not much, but while we don't need.. WE also disable mail and sms workers

for automatically updating things like:

• when an attribute is ready
• custom domain gets verified
• function build is complete
• function execution status

Ok, then I'll just remove traefik config on so, should be ok right ? While it use docker network to communicate

that won't work because then nothing would be able to connect...and the console needs to connect

Oh yes from console, I forget it..

It's from 1.3.7 no ? Cause before I havn't this errors

im pretty sure we've always used realtime in the console

Just find that it's because on local we use dev.my.company.com domain, with SSL certificate error, wich stop ServiceWorker loading. So it can't connect to realtime workers, and don't emit logs

That's why I thinks it's new 😅

FYI, in our case, realtime will not works on console (for production) cause we can only connect to console via ssh tunnel and domain set on .env file isn't a real domain. To access appwrite API, we use multiples cloudflare workers wich connect to appwrite via docker network via cloudflare tunnel. So in our case it make sense to completly disable realtime worker (having to refresh the interface isn't a big deal) but I understand that you can't fit all differents workflow.

Thinks it can be usefull to be able to completly disable realtime via project settings, like disable graphql, or (better) via .env

ya disabling realtime via project settings could be a good idea.

I update github issue accordingly