clockworklabs / clockworklabs/SpacetimeDB
Optional **rustls** TLS backend for `spacetimedb-sdk`
Nobody has claimed this yet.
- #1700 by @mamcx — closed without merging
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
spacetimedb-sdk currently hard‑codes the native-tls / OpenSSL stack. That forces every downstream project to carry a C tool‑chain and OpenSSL dev headers for each target architecture (for example, macOS → Linux ARM cross‑builds or static musl builds).
The extra native dependencies:
- Complicate CI images and local development setups
- Slow down compile times and increase binary size
- Break on minimal containers that lack OpenSSL
Providing an optional rustls backend would eliminate those external C requirements and bring spacetimedb-sdk in line with the pure‑Rust TLS defaults used by many modern networking crates.
Thanks for considering!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the spacetimedb-sdk dependency configuration and the code that selects the native-tls/OpenSSL backend. Check how an optional rustls backend could cover the stated cross-build and minimal-container cases, then verify that the SDK can build without OpenSSL when that option is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100