x402-stellar-deploy

Coordinates Heroku/Docker deployments with health checks and smoke tests for x402-stellar networks.

7|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/stellar/x402-stellar --skill x402-stellar-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x402-stellar-deploy
Source: https://github.com/stellar/x402-stellar/tree/main/.opencode/skills/x402-stellar-deploy
Command: npx skills add https://github.com/stellar/x402-stellar --skill x402-stellar-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployment of the x402-stellar project often requires coordinating multiple containers, env vars, and health checks across Heroku and Docker to ensure production readiness. This Skill provides a guided, repeatable deployment procedure that reduces setup time and minimizes misconfigurations.

Core Features & Use Cases

  • All-in-one deployment guidance for Heroku and Docker production stacks, including container orchestration and start-up sequencing.
  • Per-network configuration recommendations and validation checks to ensure secure, correct operation of facilitators, servers, and clients.
  • Release verification and smoke-test workflows to confirm successful deployment and service health in production.

Quick Start

Run the all-in-one deployment workflow in your environment and verify readiness with the provided smoke tests.

Frequently Asked Questions about x402-stellar-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Docker containers to Heroku and verify the release?

Deploy Docker containers to Heroku by coordinating containerized services, environment variables, and health checks. Release verification is handled through automated smoke tests that confirm service health and validate production readiness after rollout.

What is the best way to manage environment variables for a multi-container Docker deployment?

Managing environment variables for multi-container Docker deployment requires strict config vars and per-network configuration. This ensures secure, correct operation of facilitators, servers, and clients across different network-aware endpoints.

Why does my containerized service fail startup sequencing during deployment?

Containerized service startup sequencing fails when per-network configuration and strict config vars are not properly coordinated. Applying network-aware endpoints and validating environment variables before release ensures reliable start-up sequencing and prevents misconfigurations.

Can I use automated smoke tests to validate production readiness after a Heroku release?

Automated smoke tests validate production readiness after a Heroku release by confirming successful deployment and service health. They check whether containerized services, environment variables, and network-aware endpoints operate correctly in the production environment.

Do I need per-network configuration for deploying facilitators and clients?

Per-network configuration is required for deploying facilitators and clients to ensure secure, correct operation. Network-aware endpoints and strict config vars must be validated to coordinate containerized services and maintain production readiness across different environments.