CLI server seperation #445
Replies: 1 comment 1 reply
-
|
The server has been a point of friction for a lot of users, including myself. The initial idea was to create a simple control plane for managing sandboxes, but honestly, there are better control planes out there. From Kubernetes to nomad, we leave the control plane decision up to the user. With the ongoing rewrite, we are removing the server entirely for a more embedded approach. It improves the UX and makes it a proper library that you can use in your app, instead of a server you have to bootstrap or worry about managing its lifecycle. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋🏽
Awesome project! I was wondering why the microsandbox branch explicitly states that the CLI does not need a server? I feel like the seperating the CLI from the server architecture really helps when you are running this on a remote host. Are there any plans to bring this mode back?
Beta Was this translation helpful? Give feedback.
All reactions