Using a self-hosted Daytona sandbox instance — findings, one blocker, and workarounds

[md-abid-hussain]

What problem are you trying to solve?

I want to run TrueForge against my own Daytona instance (the Docker Compose deployment) instead of Daytona Cloud, for local development and for keeping sandbox execution inside my own infrastructure.

There's no way to tell TrueForge where that instance is — the sandbox provider manifest has no field for the API endpoint, and Settings only asks for an API key.

https://github.com/daytonaio/daytona/releases/tag/v0.190.0

[thesujai]

@md-abid-hussain I think we can add a host field in the Daytona manifest.auth.

This might not be as straight forward as it seems - as it might involve some UI change because this field will be optional and in advanced category. See if you can comeup with a plan here.

Also please avoid working on issues straight out of the box as it will waste both of our time if the plan is not clear. Please looks at our contribution guidelines https://github.com/truefoundry/trueforge/blob/main/CONTRIBUTING.md#ways-to-contribute

[md-abid-hussain]

@thesujai I only opened the draft PR for others to try how they can setup trueforge with local Daytona which I did during the hackathon.

I think I did mention that it was meant only for reference not like actual PR that's why I opened it as draft PR.

[md-abid-hussain]

I wuld like to work on this issue as well

[thesujai]

Sure @md-abid-hussain, give it a shot. First step might be to see if it requires any UI changes for marking the host field optional.

[md-abid-hussain]

@thesujai
The external package @truefoundry-agents-assistant-ui-runtime defines the sandbox config type

/** Mutable sandbox provider settings shared by catalog rows, create, and update. */
interface SandboxConfig {
    execTimeoutMs: number;
    autoStopIntervalInMinutes: number;
    autoArchiveIntervalInMinutes: number;
    autoDeleteIntervalInMinutes: number;
}

• add apiUrl?: string to SandboxConfig in the external runtime package.
  OR
• extend the relevant runtime sandbox types locally in trueforge-ui, then remove those local extensions once the external package is updated.

[thesujai]

I think first we will need to remove the dependency from @truefoundry-agents-assistant-ui-runtime before starting on this. Trueforge should be the source of all the SandboxConfig. We will get this sorted before you can start any work here, so please hold off any implementation for now.

@md-abid-hussain Thanks for finding this:)