clockworklabs / clockworklabs/SpacetimeDB
Determine necessary features for running standalone in prod
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
We want it to be reasonable for small-scale users to self-host SpacetimeDB-standalone in production, but we haven't really done the work of determining what's necessary to get there.
Notably, someone in the Discord asked about restricting who can publish. It's obviously undesirable for anyone to be able to publish modules to a production STDB instance which is meant to be serving a single app.
I'm sure there are many other features we're missing. Probably we can crowdsource the list.
Assigning this to the UX team because it's a matter of determining users' needs.
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
This issue names no files, tests, or entry points; start by reviewing the standalone production workflow and the Discord concern about restricting module publication. Done means producing an agreed, prioritized list of features needed for small-scale production self-hosting, including who may publish modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authorization, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100