runtm-worker
Build and deploy worker for Runtm. See the self-hosting docs for deployment setup.
Pipeline
Remote Builder (Default, Recommended)
- Unzip artifact from storage
- Validate manifest against schema
- Create Fly app and allocate IPs
- Run
flyctl deploy(builds AND deploys in one step)- Auto-generates
fly.tomlwith optimized health checks - Builds on Fly's remote builders (fast, no local Docker)
- Deploys to Fly Machine with health check verification
- Auto-generates
- Save provider resource and verify health
- Update deployment status + URL in DB
- Persist logs
Local Build (Fallback)
- Unzip artifact from storage
- Validate manifest against schema
- Build Docker container locally with BuildKit
- Push to Fly.io registry
- Create/update Fly Machine via Machines API
- Poll for health check
- Update deployment status + URL in DB
- Persist logs
Development
# Install dependencies
pip install -e ".[dev]"
# Run worker
python -m runtm_worker.main
# Run tests
pytest
Environment Variables
| Variable | Description | Default |
|---|---|---|
DATABASE_URL |
PostgreSQL connection string | Required |
REDIS_URL |
Redis connection string | Required |
FLY_API_TOKEN |
Fly.io API token | Required |
ARTIFACT_STORAGE_PATH |
Local artifact storage path | /artifacts |
ARTIFACT_STORAGE_BACKEND |
Storage backend: local or s3 |
local |
BUCKET_NAME |
S3/Tigris bucket name (when backend=s3) | - |
AWS_ENDPOINT_URL_S3 |
S3 endpoint URL (e.g. https://fly.storage.tigris.dev) |
- |
USE_REMOTE_BUILDER |
Use Fly's remote builder (faster) | true |
Providers
The worker uses a provider interface to support multiple deployment backends:
FlyProvider- Fly.io Machines (default)- Future: Cloud Run, etc.
Note: When using the remote builder (default), most deployment is handled by
flyctl deploy. The FlyProvider is still used for app creation, IP allocation,
machine listing, health verification, and custom domain management.
1 maintainer
Metadata
1 maintainer
Release files for runtm-worker 0.2.163
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 | |
|---|---|---|---|---|
| runtm_worker-0.2.163.tar.gz | 49.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runtm_worker-0.2.163-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 94.6 kB
Release files / runtm_worker-0.2.163.tar.gz
| Download URL | runtm_worker-0.2.163.tar.gz |
|---|---|
| Size | 49.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a93eee7728f6b2b321cdd4265ca6a6d3de1233f226a41906e9d15f5f5ed120d
|
|
BLAKE2b-256 checksum How to use checksums |
818685db3619cb7f3d182a65af2dac50a6468d4e0144a4be49f0e725a9de111a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / runtm_worker-0.2.163-py3-none-any.whl
| Download URL | runtm_worker-0.2.163-py3-none-any.whl |
|---|---|
| Size | 45.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33e25d5a35b80a88b25c7813bddc1c5121657d98aaa1c563d355c5316f6c3f12
|
|
BLAKE2b-256 checksum How to use checksums |
efac2a30d99bf3ef03aff521620daa2d7e4065efd5cce30e4769a7819829242d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for runtm-worker 0.2.163
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.
