Does anyone know of similar solutions that can be self-hosted? (without a 12 service stack like Daytona [1])
Code and Let Live
151–160 of 195 posts
Re: Code and Let Live
#152i dont think i really get what this gives me over docker. everything i read is how i work for years
Docker does not and cannot offer full isolation. A sandboxed VM on someone else's computer is less likely to be problematic for running untrusted code than a container on your system.
seems not to justify submitting to a proprietary single vendor solution where users are locked into opaque checkpoints they forgot how to migrate away from. this is not something made for users lets be clear. there are tens or hundreds of vm layers for defense in depth for docker so thats a non argument, no one says docker has to provide security its for tooling and common practices that allow vendor independence and moving to self hosted stacks as needed!
Re: Code and Let Live
#153Earlier quoted context omitted.
It's coming, and it'll make sense how and why next week when I run the "how this shit works" post. I actually pushed to include it in the launch release. You'd have to ask Kurt why he didn't, but I think the idea is just to get more real-world usage first.
Do you expect that to replace git worktree for getting Claude to work on multiple things in parallel? That was something I was curious about watching the demo video.
Can’t edit, but adding I noticed that there’s a limit of 3 sprites running concurrently for pay as you go, so that’s probably not a realistic day-to-day workflow.
Re: Code and Let Live
#154This is cool but like...a docker container running locally works fine too?
Re: Code and Let Live
#155Putting aside the details of the product itself, I love the style of this post. I wish more announcements read like this.
Re: Code and Let Live
#156I really want to love this, but my experience in the first 20 seconds is unfortunately like some of my other experiences coding against Fly APIs, they're broken. https://sprites.dev/api has this command: $ curl -X POST " https://api.sprites.dev/v1/sprites " \ -H "Authorization: Bearer $SPRITES_TOKEN" \ -d '{"name": "my-sprite"}' which responds with {"error":"name is required"} if you use the request body in the full…
Believe it or not, that's the only example that's not autogenerated from tests (yet).
https://github.com/superfly/sprites-js/tree/main/examples https://github.com/superfly/sprites-go/tree/main/examples https://github.com/superfly/sprites-py/tree/main/examples https://github.com/superfly/sprites-ex/tree/main/examples
Re: Code and Let Live
#157Philosophically, I like Fly and have been a customer since very early on. That said, I dread having to do anything CLI related, which for hobby projects is like once every few weeks. Glancing at the docs for Sprite, I worry that this will be another CLI where a good 95% of the time that I go to invoke a command, my workflow is interrupted by an auto-updater that takes longer than whatever interaction I'm trying to do…
flyctl is complicated and, unfortunately, needs pretty aggressive auto updates. The sprite CLI should be much better in this respect.
Re: Code and Let Live
#158This is seriously cool - it's exactly the DX and API I've been waiting for from sandboxed execution providers. I'd love to be able to configure the base image/VM in a way that doesn't bundle coding tools or anything else I don't need, and comes with some other binaries installed (I'm more interested in using this as an API for a sandbox use-case I have). Is there a way to do this at the moment / is this on the roadma…
This is on the roadmap. The open question right now is if we can just do "fork from checkpoint" for customized template environments, or if we need all the docker infrastructure.
If the fat bundled environment harmful for you, or just extra stuff you don't care about?
Re: Code and Let Live
#159I liked this idea so much I signed up and linked my personal cc (to my job email) to try it out. Unfortunately, it keeps saying "You must add a credit card to use Sprites with this organization" - even though I just linked a card. No way to continue from there: it's a loop that shows my account with an "activate" button, clicking it shows the error and my account again. Fly.io says I have an account now and it's "in…
This did resolve itself.. I guess adding the card took.. a few minutes? Errors were confusing tho
Re: Code and Let Live
#160This is seriously cool - it's exactly the DX and API I've been waiting for from sandboxed execution providers. I'd love to be able to configure the base image/VM in a way that doesn't bundle coding tools or anything else I don't need, and comes with some other binaries installed (I'm more interested in using this as an API for a sandbox use-case I have). Is there a way to do this at the moment / is this on the roadma…
This is on the roadmap. The open question right now is if we can just do "fork from checkpoint" for customized template environments, or if we need all the docker infrastructure. If the fat bundled environment harmful for you, or just extra stuff you don't care about?
Not harmful for now - "fork from checkpoint" would be perfectly fine for me at the moment. The main issue (as flagged in the post) is that setting up additional tooling can take a while!
In the longer term, docker is nice from a reproducibility + CI perspective, and a docker build is already something can easily work with and track in my system.
One thing I've heard but not verified with other sandboxed execution providers is that startup times for custom images can be quite slow, so it could be a potential differentiator given Fly's existing infra.