Hi all! I'm a systems administrator tasked with ru...
# spicedb
a
Hi all! I'm a systems administrator tasked with running a SpiceDB backend for some of my devs and they're asking whether the Playground can be self-hosted and connected to our live spicedb backend for testing/verification/visualisation. Couldn't find anything concrete other than this: https://github.com/authzed/spicedb/issues/1075 — so I decided to ask here 😉
v
Yeah, that is the case, we've been discussing opensourcing the playground. However, the playground itself does not act as a frontend to the state of your SpiceDB. It runs it's own SpiceDB using WASM. authzed.com offers a mechanism to import part of that state in your live SpiceDB into the playground.
a
OK, I see, thanks @vroldanbet!
But, even without the frontend/backend distinction, would it be possible to compile and run a "private" instance of the Playground?
v
no, it's not possible because it's not opensource, and we have decided if and when we will opensource it
The playground is completely client-side based. The only state kept is when you "share"
otherwise, everything is happening in your browser.
a
OK, excellent, thanks. I'll pass that info onto my devs. 🙂
v
we definitely want to understand better what motivations there are to need a private playground, so we would appreciate all information in this regard 🙏🏻
but if the concern is "feeling uneasy about putting intellectual property in the playground", I can only say that the playground is all client based, and it only submits data to our servers when you decide to click the "share button"
a
Yeah, I think we're totally fine with that, the request's original premise was more about connecting the playground to a "real" SpiceDB instance, but if that's not possible I don't think they'll have a problem using the non-selfhosted Playground running fully in the browser.
So until you can connect the frontend to something else than the internal WASM spicedb instance there's no real-world need for self-hosting it 🙂
As far as I can see, at least.
v
alright so I guess what I'm hearing is that your devs would like to be able to use the playground as a way to tinker with the state of a specific playground instance. I think that's valuable product feedback FYI @jzelinskie @dsieczko
do you know if they'd would want to use it as fronted even for a large-scale production SpiceDB deployment? or is just for stage-envs or development
a
Possibly for a full-scale production SpiceDB instance, as a kind of auxiliary IDE, a tool to visualise/tinker/reason about/debug real life data we'll be handling in the long run, especially once we go live with our authz setup. For a start it'd be great if we could do the same with a stage-env/development instance. 🙂
v
Coolio, I think that makes sense, although perhaps we can do better than just playground for a prod debug / IDE. Thanks for the feedback!
j
@antoszka if we do OSS playground, then we do have some ideas on how it could connect to a local SpiceDB
a
Excellent! I'd be most happy to work on deployment and testing
j
In the mean time, zed can be used to poke around live systems: https://github.com/authzed/zed