Daft Cloud SDK
Usage
# Initialize a project
ev init
# Run a workflow
ev run my_module.py
# Configure a profile e.g. staging with endpoint overrides
ev configure
Installation
The CLI is installed in the project's virtualenv. It can also be added to a project's pyproject.toml with ev-sdk = { path = "../ev-cloud/ev-sdk", editable = true }.
You can also run CLI with uv via uv run ev <command>.
dependencies = [ "ev-sdk" ]
[tool.uv.sources]
ev-sdk = { path = "../ev-cloud/ev-sdk", editable = true }
Configuration
The configuration uses profiles and is located at ~/.ev/config.toml (or $EV_HOME/config.toml).
[default]
profile = "default"
[profiles.default]
endpoint_url = "https://api.daft.ai"
dashboard_url = "https://cloud.daft.ai"
[profiles.development]
endpoint_url = "http://localhost:3000"
dashboard_url = "http://localhost:3003"
[profiles.staging]
endpoint_url = "https://staging.api.daft.ai"
dashboard_url = "https://staging.cloud.daft.ai"
Configuration Fields
endpoint_url: API endpoint URL (defaults tohttps://api.daft.aiif not specified)dashboard_url: Dashboard UI URL for run links (defaults tohttps://cloud.daft.aiif not specified)
Manual Configuration
While ev configure sets up profile configuration, you can manually edit your config file to:
- Add custom
endpoint_urlanddashboard_urlvalues for different environments - Create multiple profiles for testing, staging, and production
- Switch between local development and hosted environments
Commands
# Interactive configuration wizard
ev configure
# Initialize project in current repository
ev init [--template TEMPLATE]
# Run python scripts on Daft Cloud
ev run script.py # Python file
ev run module # Python module
ev run module:function --key=value # Function with args
# List resources
ev list projects
# Use specific profile
ev --profile work run script.py
Provider
The Daft Provider is a simple implementation of the Provider interface with a set of known implementations that are resolved against our control plane.
We can move this into open source post launch, but it doesn't make a difference.
Configuration
We inject these environment variables to trigger using the Daft Provider.
DAFT_PROVIDER="daft"
DAFT_PROVIDER_BASE_URL="https://...."
DAFT_PROVIDER_API_KEY="sk-..."
| Stage | Endpoint |
|---|---|
| Tilt | n/a |
| Staging | https://ai-eventual-provider-staging.onrender.com/ |
| Production | n/a |
Metadata
Release files for ev-sdk 0.1.5
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 | Actions |
|---|---|---|---|---|
| ev_sdk-0.1.5.tar.gz | 40.5 kB | Without provenance | Details for ev_sdk-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ev_sdk-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for ev_sdk-0.1.5-py3-none-any.whl |
Total release size: 87.6 kB
Release files / ev_sdk-0.1.5.tar.gz
| Download URL | ev_sdk-0.1.5.tar.gz |
|---|---|
| Size | 40.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62321b54ac27d4062fee190487f8bc54e57726877089d4591d0ea4ac31617b20
|
|
BLAKE2b-256 checksum How to use checksums |
298fd9f2841205b76fddfd32416472d3e04627f828313630437fb4df0e155eb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / ev_sdk-0.1.5-py3-none-any.whl
| Download URL | ev_sdk-0.1.5-py3-none-any.whl |
|---|---|
| Size | 47.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6398e7765bdbf8c852845377fc8b6f138833147e60b9c9363310d9249dfdda98
|
|
BLAKE2b-256 checksum How to use checksums |
6121e01e7763f08b536a5b511f8fa99bae9ca6e8bf5797270c0f79aee49607d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for ev-sdk 0.1.5
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.