-
Notifications
You must be signed in to change notification settings - Fork 493
Allow building custom standalone servers #2416
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
base: master
Are you sure you want to change the base?
Allow building custom standalone servers #2416
Conversation
ControlDb
and members of StandaloneEnv
struct
@jdetter lmk how I can go about signing the CLA |
@m1guelpf Could you send me an email to |
@m1guelpf We're happy to move forward with this. Just a note: While we guarantee API/ABI stability for future |
(also it looks like we have some merge conflicts now - if you can get those fixed, we should be good to go!) |
@bfops resolved the conflicts! crate stability is not an issue for me, I was planning to pin to a commit anyways 😁 |
Hey @m1guelpf - based on the test failures, it looks like some more crates need updating. |
Description of Changes
Expands the
spacetimedb-standalone
crate to also serve as a library to build your own standalone servers with custom auth services and more. This is accomplished by:StandaloneEnv
instead of having to recreate it from scratch.StandaloneEnv
abstract over anyJwtAuthProvider
and not just the default (but still default toDefaultJwtAuthProvider
, so no API changes for existing clients)API and ABI breaking changes
I don't believe this includes any breaking changes, other than some of the crate's API now being public. Since the crate is currently marked as unstable, this should be fine.
Expected complexity level and risk
Changes are very simple.
Testing
I'm using this branch locally to develop a custom SpacetimeDB server with stricter authentication requirements.