This commit is contained in:
marko-kraemer 2025-05-18 21:25:15 +02:00
parent 2af572ab03
commit 0148c03ec5
3 changed files with 15 additions and 2 deletions

View File

@ -30,7 +30,7 @@ class SandboxBrowserTool(SandboxToolsBase):
await self._ensure_sandbox()
# Build the curl command
url = f"http://localhost:8003/api/automation/{endpoint}"
url = f"http://localhost:8002/api/automation/{endpoint}"
if method == "GET" and params:
query_params = "&".join([f"{k}={v}" for k, v in params.items()])

View File

@ -20,6 +20,7 @@ You can modify the sandbox environment for development or to add new capabilitie
```
cd backend/sandbox/docker
docker compose build
docker push kortix/suna:0.1.2
```
3. Test your changes locally using docker-compose
@ -30,3 +31,15 @@ To use your custom sandbox image:
1. Change the `image` parameter in `docker-compose.yml` (that defines the image name `kortix/suna:___`)
2. Update the same image name in `backend/sandbox/sandbox.py` in the `create_sandbox` function
3. If using Daytona for deployment, update the image reference there as well
## Publishing New Versions
When publishing a new version of the sandbox:
1. Update the version number in `docker-compose.yml` (e.g., from `0.1.2` to `0.1.3`)
2. Build the new image: `docker compose build`
3. Push the new version: `docker push kortix/suna:0.1.3`
4. Update all references to the image version in:
- `backend/utils/config.py`
- Daytona images
- Any other services using this image

View File

@ -159,7 +159,7 @@ class Configuration:
STRIPE_PRODUCT_ID_STAGING: str = 'prod_SCgIj3G7yPOAWY'
# Sandbox configuration
SANDBOX_IMAGE_NAME = "kortix/suna:0.1.2.4"
SANDBOX_IMAGE_NAME = "kortix/suna:0.1.2.5"
SANDBOX_ENTRYPOINT = "/usr/bin/supervisord -n -c /etc/supervisor/conf.d/supervisord.conf"
@property