DBDelve
Dive deep into your data. A fast, native, multi-engine database client written in Rust. Free and open source, no telemetry.
翻譯準備中
One config, one CLI, all targets. Deploy to GCP, AWS, Azure, Cloudflare, npm, and Homebrew from a single YAML file.
翻譯準備中
正在載入完整 README。
檢視完整 README ↗A cloud-agnostic build and deployment CLI. Define your service once, deploy to any cloud provider.
pilum deploy --tag=v1.0.0
Pilum handles the build → push → deploy pipeline while your infrastructure-as-code (Terraform, Pulumi) defines the actual resources.
Pilum is dogfooded as the deployment tool for every SID Technologies product — dozens of services shipped to Cloud Run, Cloud Run Jobs, Cloudflare Pages, npm, and Homebrew with it, daily, since December 2025.
Provider status, honestly:
Not sure Pilum fits your stack? Read When to Use Pilum (and When Not To) — it includes the cases where the answer is no.
brew tap sid-technologies/pilum
brew install pilum
go install github.com/sid-technologies/pilum@latest
depends_on across servicesenvironments blockUse the interactive init command to generate a pilum.yaml:
pilum init
This walks you through:
Create a pilum.yaml in your project:
# yaml-language-server: $schema=https://raw.githubusercontent.com/SID-Technologies/pilum/main/schemas/pilum.yaml.schema.json
name: my-api
provider: gcp
project: my-gcp-project
region: us-central1
registry_name: gcr.io/my-gcp-project
build:
language: go
version: "1.23"
pilum check
This validates your pilum.yaml against the recipe's required fields and the JSON Schema:
cloud_run.cpu_throtling (with a "did you mean" suggestion), or a value of the wrong type that Pilum would ignore, such as min_instances: "2". environments blocks are checked too.version: 1.20 reads as 1.2; quote it).Other commands print the same problems as warnings and carry on.
# Deploy all services
pilum deploy --tag=v1.0.0
# Deploy specific service
pilum deploy my-api --tag=v1.0.0
# Preview without executing
pilum deploy --dry-run --tag=v1.0.0
# Build and push only (no deploy)
pilum publish --tag=v1.0.0
Pilum uses a cooking metaphor: recipes define deployment workflows, ingredients generate cloud-specific commands.
Each recipe defines:
pilum.yaml must contain| Recipe | Provider | Description |
|---|---|---|
gcp-cloud-run | gcp | Deploy to Google Cloud Run |
gcp-cloud-run-job | gcp | Deploy batch jobs to Google Cloud Run Jobs |
gcp-mig-container | gcp | Roll a new container image onto an existing managed instance group (COS + startup script) |
aws-lambda | aws | Deploy to AWS Lambda |
azure-container-apps | azure | Deploy to Azure Container Apps |
cloudflare-pages | cloudflare | Deploy to Cloudflare Pages |
homebrew | homebrew | Publish Homebrew formula |
npm | npm | Publish npm packages |
Use pilum recipes to list all recipes, or pilum recipes <name> to see required fields, optional fields, and deployment steps for a specific recipe.
Create your own recipes in recipes/:
以上為 README 的開頭部分。其餘內容請閱讀原文。 檢視完整 README ↗