No description
Find a file
Jeremie Fraeys d6c8ca66d0
Some checks failed
Documentation / build (push) Has been cancelled
License Check / license-check (push) Has been cancelled
Documentation / deploy (push) Has been cancelled
first commit
2026-01-18 22:16:16 -05:00
.github ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
.local-artifacts Fix multi-user authentication and clean up debug code 2025-12-06 12:35:32 -05:00
build ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
cli feat(cli): add validate/info commands and improve protocol handling 2026-01-05 12:31:20 -05:00
cmd ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
configs chore(ops): reorganize deployments/monitoring and remove legacy scripts 2026-01-05 12:31:26 -05:00
db feat: add GitHub workflows and development tooling 2025-12-04 16:56:25 -05:00
deployments chore(ops): reorganize deployments/monitoring and remove legacy scripts 2026-01-05 12:31:26 -05:00
docs docs: update architecture/queue pages and remove legacy development setup 2026-01-05 13:26:39 -05:00
examples Slim and secure: move scripts, clean configs, remove secrets 2025-12-07 13:57:51 -05:00
internal feat(experiment): improve experiment lifecycle and update first-experiment guide 2026-01-05 12:37:34 -05:00
monitoring chore(ops): reorganize deployments/monitoring and remove legacy scripts 2026-01-05 12:31:26 -05:00
podman chore(ops): reorganize deployments/monitoring and remove legacy scripts 2026-01-05 12:31:26 -05:00
redis Slim and secure: move scripts, clean configs, remove secrets 2025-12-07 13:57:51 -05:00
scripts chore(ops): reorganize deployments/monitoring and remove legacy scripts 2026-01-05 12:31:26 -05:00
tests test: expand unit/integration/e2e coverage for new worker/api behavior 2026-01-05 12:31:36 -05:00
tools chore(ops): reorganize deployments/monitoring and remove legacy scripts 2026-01-05 12:31:26 -05:00
.dockerignore chore(repo): add dockerignore, changelog, and ignore local artifacts 2026-01-05 12:30:57 -05:00
.env.example chore(repo): add dockerignore, changelog, and ignore local artifacts 2026-01-05 12:30:57 -05:00
.flake8 feat: initialize FetchML ML platform with core project structure 2025-12-04 16:52:09 -05:00
.gitignore chore(repo): add dockerignore, changelog, and ignore local artifacts 2026-01-05 12:30:57 -05:00
.golangci.yml ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
.golintrc Fix multi-user authentication and clean up debug code 2025-12-06 12:35:32 -05:00
.pylintrc feat: initialize FetchML ML platform with core project structure 2025-12-04 16:52:09 -05:00
CHANGELOG.md chore(repo): add dockerignore, changelog, and ignore local artifacts 2026-01-05 12:30:57 -05:00
DEVELOPMENT.md ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
go.mod feat(api): refactor websocket handlers; add health and prometheus middleware 2026-01-05 12:31:07 -05:00
go.sum feat(api): refactor websocket handlers; add health and prometheus middleware 2026-01-05 12:31:07 -05:00
LICENSE ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
Makefile ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00
pyproject.toml feat: initialize FetchML ML platform with core project structure 2025-12-04 16:52:09 -05:00
README.md first commit 2026-01-18 22:16:16 -05:00
SECURITY.md ci: align workflows, build scripts, and docs with current architecture 2026-01-05 12:34:23 -05:00

FetchML

A lightweight ML experiment platform with a tiny Zig CLI and a Go backend. Designed for homelabs and small teams.

FetchML publishes pre-built release artifacts (CLI + Go services) on GitHub Releases.

If you prefer a one-shot check (recommended for most users), you can use:

./scripts/verify_release.sh --dir . --repo <org>/<repo>
  1. Download the right archive for your platform

  2. Verify checksums.txt signature (recommended)

The release includes a signed checksums.txt plus:

  • checksums.txt.sig
  • checksums.txt.cert

Verify the signature (keyless Sigstore) using cosign:

cosign verify-blob \
  --certificate checksums.txt.cert \
  --signature checksums.txt.sig \
  --certificate-identity-regexp "^https://github.com/<org>/<repo>/.github/workflows/release.yml@refs/tags/v.*$" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  checksums.txt
  1. Verify the SHA256 checksum against checksums.txt

  2. Extract and install

Example (CLI on Linux x86_64):

# Download
curl -fsSLO https://github.com/<org>/<repo>/releases/download/<tag>/ml-linux-x86_64.tar.gz
curl -fsSLO https://github.com/<org>/<repo>/releases/download/<tag>/checksums.txt
curl -fsSLO https://github.com/<org>/<repo>/releases/download/<tag>/checksums.txt.sig
curl -fsSLO https://github.com/<org>/<repo>/releases/download/<tag>/checksums.txt.cert

# Verify
cosign verify-blob \
  --certificate checksums.txt.cert \
  --signature checksums.txt.sig \
  --certificate-identity-regexp "^https://github.com/<org>/<repo>/.github/workflows/release.yml@refs/tags/v.*$" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  checksums.txt
sha256sum -c --ignore-missing checksums.txt

# Install
tar -xzf ml-linux-x86_64.tar.gz
chmod +x ml-linux-x86_64
sudo mv ml-linux-x86_64 /usr/local/bin/ml

ml --help

Quick start

# Clone and run (dev)
git clone <your-repo>
cd fetch_ml
make dev-up

# Or build the CLI locally
cd cli && make all
./zig-out/bin/ml --help

What you get

  • Zig CLI (ml): Tiny, fast local client. Uses ~/.ml/config.toml and FETCH_ML_CLI_* env vars.
  • Go backends: API server, worker, and a TUI for richer remote features.
  • TUI over SSH: ml monitor launches the TUI on the server, keeping the local CLI minimal.
  • CI/CD: Crossplatform builds with zig build-exe and Go releases.

CLI usage

# Configure
cat > ~/.ml/config.toml <<EOF
worker_host = "127.0.0.1"
worker_user = "dev_user"
worker_base = "/tmp/ml-experiments"
worker_port = 22
api_key = "your-api-key"
EOF

# Core commands
ml status
ml queue my-job
ml cancel my-job
ml dataset list
ml monitor  # SSH to run TUI remotely

Phase 1 (V1) notes

  • Task schema supports optional snapshot_id (opaque identifier) and dataset_specs (structured dataset inputs). If dataset_specs is present it takes precedence over legacy datasets / --datasets args.
  • Snapshot restore (S1) stages verified snapshot_id into each task workspace and exposes it via FETCH_ML_SNAPSHOT_DIR and FETCH_ML_SNAPSHOT_ID. If snapshot_store.enabled: true in the worker config, the worker will pull <prefix>/<snapshot_id>.tar.gz from an S3-compatible store (e.g. MinIO), verify snapshot_sha256, and cache it under data_dir/snapshots/sha256/<snapshot_sha256>.
  • Prewarm (best-effort) can fetch datasets for the next queued task while another task is running. Prewarm state is surfaced in ml status --json under the optional prewarm field.
  • Env prewarm (best-effort) can build a warmed Podman image keyed by deps_manifest_sha256 and reuse it for later tasks.

Changelog

See CHANGELOG.md.

Build

# CLI (Zig)
cd cli && make all      # release-small
make tiny              # extra-small
make fast              # release-fast

# Go backends
make cross-platform    # builds for Linux/macOS/Windows

Deploy

  • Dev: docker-compose up -d
  • Prod: Use the provided systemd units or containers on Rocky Linux.

Docs

See docs/ for detailed guides:

  • docs/src/zig-cli.md CLI reference
  • docs/src/quick-start.md Full setup guide
  • docs/src/deployment.md Production deployment

Source code

The FetchML source code is intentionally not hosted on GitHub.

The canonical source repository is available at: <SOURCE_REPO_URL>.

Contributing

Contributions are welcome.

  • Questions / bug reports: Use GitHub Issues: <GITHUB_ISSUES_URL>. Include:
    • how to reproduce
    • expected vs actual behavior
    • logs/config snippets (sanitize secrets)
    • OS + versions (Go, Zig, Podman/Docker if relevant)
  • Changes: Submit a patch in a GitHub issue.
    • Create a topic branch.
    • Run tests/linters.
    • Export your change as either:
      • a patch series: git format-patch -N origin/main, or
      • a single bundle: git bundle create fetchml.bundle origin/main..HEAD
    • Attach the generated files to a GitHub issue at <GITHUB_ISSUES_URL>.

License

FetchML is source-available for transparency and auditability. It is not open-source.

See LICENSE.