agentix-deployment-daytona
Daytona deployment backend for Agentix.
Status: CLI surface in place; the managed-sandbox integration is still a stub. Tracking parity with
DockerDeployment(live runtime URL,lifecycle()context manager) before promoting to a 1.0 release.
Install
pip install agentix-deployment-daytona
Set DAYTONA_API_KEY in the environment.
Use
agentix deploy daytona --image my-agent:0.1.0
from agentix import RuntimeClient, SandboxConfig
from agentix.deployment.daytona import DaytonaDeployment
async with DaytonaDeployment().lifecycle(
SandboxConfig(image="my-agent:0.1.0")
) as sandbox:
async with RuntimeClient(sandbox.runtime_url) as c:
...
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for agentix-deployment-daytona 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agentix_deployment_daytona-0.1.0.tar.gz | 2.6 kB | Without provenance | Details |
Release files / agentix_deployment_daytona-0.1.0.tar.gz
| Download URL | agentix_deployment_daytona-0.1.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c8ba3e486e9a4e4bb1f8a6cd5738889f54d8db35a269177b2eee535d663cc08
|
|
BLAKE2b-256 checksum How to use checksums |
3867047dc8ec56b01af74a6f4cf07eb1fbf3438edede4921ed75bc4344e5a9a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Security for agentix-deployment-daytona 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
