Open oshoemaker opened 1 year ago
Sure, I'm open to the idea. I'm not sure why you would want both the client and server installed in the same project though.
There is a use case that having a headless client participating in the session can be beneficial. It allows a low overhead communication mechanism for controlling the session without the need for other external services. We may end up using the go SDK or Rust so this isn't high priority. I do have both working in the same client using a this SDK as a local module and seems to work well.
yeah this makes sense.. we are thinking about folding this package into a monorepo for both of our python SDKs.
The package names would be:
livekit.rtc
in codelivekit.api
in codeCC: @theomonnom
i am having problems installing now , how to install this from pypi? better just do mono repo and have single package for both client and server should be better
Hey, we’re going to release a Server SDK inside the client repo this week (mono repo, but different packages)
Is it possible to rename this project to "livekitserver" or something similar so it does not conflict with the Python Client SDK?