7 documents tagués avec "deploy-action"

The canonical CHIP-0035 wasm builder constructs every store-coin spend; admin / writer / oracle delegation is the on-chain primitive behind Teams and revocable CI deploy tokens — never hand-rolled.

Index en une page des entités essentielles du DIG Network — capsule, store, generation, URN, retrieval key, le dig RPC, le protocole chia://, et l'ancrage on-chain — chacune définie une fois et reliée à sa documentation détaillée.

Auto-publish your built site or dapp to your existing DIG store on every push with the dig-network/deploy-action — git-push-to-deploy, free PR previews, and a PR comment + GitHub deployment status. Keyless CI auth, no long-lived hub secret.

Give your CI or an agent a revocable key that can publish new versions of your store — but never your wallet seed, and never the power to change ownership. Issue it once in DIGHUb, drop it into CI as DIGSTORE_WRITER_KEY, and revoke it any time.

Une plateforme entièrement lisible par machine — OpenAPI/OpenRPC, une taxonomie d'erreurs cataloguée, une tarification en direct, JWKS, du JSON par page, et un @dignetwork/dig-sdk typé — pour câbler un portefeuille + des lectures vérifiées dans votre application sans avoir à extraire la moindre ligne de prose humaine.

The shortest path for integrating developers: connect a wallet, read verified content, build a spend the right way, and deploy from CI — using the typed @dignetwork/dig-sdk and the dig RPC, no prose-scraping required.

Register an HTTPS endpoint to be notified when a deployment changes state — queued, building, ready, or error. Each event is signed so you can verify it came from DIGHUb. The event contract — payload shape and signature — is stable; delivery is rolling out.