rusch

6 ms·

1. 1.▲
   by rusch 13d ago

   It's at the level where calling it a sandbox is a lie
2. 2.▲
   by rusch 1mo ago

   Yes correct. We don't use git hooks so they are globally disabled. I also see they added host worktree mode which could work well with superset since it creates the worktrees. https://docs.docker.com/ai/sandboxes&#
3. 3.▲
   by rusch 1mo ago

   Currently running codex. I run one sandbox per repo. So I create the sandbox in the repo root. Then it's a custom terminal preset: sbx run --name "yoursandbox" -- --cd "$PWD" This boots a sbx session in the worktree
4. 4.▲
   by rusch 1mo ago

   The env var is just a placeholder in the VM, so no real secret is in there.
5. 5.▲
   by rusch 1mo ago

   Yes, the stated "target workload"[0] is not what i'm looking for. I want my agent to run for long, spin up dedicated local stack while developing etc. It seems with gondoling i need to explain the agent to run commands in the
6. 6.▲
   by rusch 1mo ago

   The login is annoying but, lacking an open source alternative, this has been my daily driver for a while now because it works great out of the box with two key features: outbound firewall and secret injection with placeholders. I run it wit
7. 7.▲
   by rusch 5mo ago

   I wonder when and if microplastics will get it's Asbestos moment. Obviously they are not as carcinogenic, but it seems we don't have the full picture, and microplastics are present at an insanely higher degree than asbestos where.