Skip to content

Switch Y-WebSocket server from Node to Python #1039

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

davidbrochart
Copy link

Closes #728.

@davidbrochart davidbrochart marked this pull request as draft June 3, 2025 10:13
@davidbrochart
Copy link
Author

8e8c18f replaces the Node-based Y-WebSocket server with a minimal pycrdt-websocket server.
For now, this Python server has to be run manually with:

python src/backend/servers/y-provider/server.py

This currently needs y-crdt/pycrdt-websocket#130.

@davidbrochart
Copy link
Author

davidbrochart commented Jun 3, 2025

With 5709d9b there is no need to manually start the Python server anymore, it's integrated in Docker.

@lunika
Copy link
Member

lunika commented Jul 4, 2025

Hi,
I was wondering if it's possible to integrate it with the current django application or not ? Otherwise I don't see advantage to switch from node to python.

@davidbrochart
Copy link
Author

Sure, the goal is to get rid of the separate Python server and integrate it with the Django application. It's easy if the Django server is ASGI. I understood that it's currently WSGI but that you are planning to switch to ASGI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why Yjs server in ts when you can use pycrdt instead ?
4 participants