The workflow passed static publication checks, but download remains disabled until its license and final release manifest are approved.
The outcome
Complete a bounded release on an existing multi-app host while protecting neighboring workloads, persistent data, ingress, secrets, capacity, and rollback evidence.
Use it when
- Use when an application must be deployed or upgraded on an existing Linux server that already runs other projects through Docker Compose or system services.
- Use when shared Caddy, Nginx, or Traefik ingress must be extended safely and the new release plus every protected neighboring service must be verified.
It does not do
- Does not replace the user’s final authorization for project scope, account access, external changes, or business consequences.
- Does not represent repository static checks as runtime certification across every platform, provider account, or production environment.
Inputs
- Approved SSH host/profile, project and environment, source revision and artifacts, runtime topology, public hostnames, migrations, expected behavior, and protected services.
- Protected runtime access, capacity and health observations, secret identifiers, and backup/recovery evidence required by the release.
Outputs
- Validated deployment manifest with isolation, capacity, migration, ingress, downtime, neighbor, verification, and rollback impact.
- Deployed or recovered release evidence including exact artifact identity, layered application checks, protected-service comparison, and remaining risk.
Natural-language triggers
Use $shared-host-app-deployer to deploy this staging Compose project to the existing server, add its Caddy route, and prove all three current applications remain healthy.
Use $shared-host-app-deployer to upgrade this production image by digest, run the one-shot migration, verify TLS and business health, and roll back safely if acceptance fails.
Permission map
Environment & requirements
Agents
- Codex
- Claude Code
Platforms
- macOS
- Linux
- Windows
Required tools
- SSH
- Docker Compose
- reverse proxy
- Git
Data handling
May read server services, ports, logs, configuration, and deployment state; SSH private keys, environment values, and neighboring-service data must not enter public artifacts.
Credential handling
Uses only existing secure credential channels authorized by the user; tokens, keys, cookies, private keys, and real user data must not be copied into the Skill, logs, reports, or public artifacts.
Verification evidence
Passed repository structure, bilingual metadata, and reference checks; this Skill has not entered candidate-artifact generation or runtime verification.
- Level
- Checked
- Checked
- 2026-10-12
- Expires
- 2027-01-10
- Source revision
fac86e9d2646
Environment
- Repository structure and metadata validation on macOS
Targets checked
- source metadata
- package structure
Evidence IDs
public-catalog-schema-v3source-repository-validation
Limits & support
Known limitations
- The current verification level is a repository static check, not an end-to-end validation against a real provider account, physical device, or production environment.
- Agents, platforms, and provider interfaces continue to change; each run must inspect current state and respect explicit confirmation gates.
Permission changes
- No permission change is declared for this release; for a first public release, the permission map on this page is authoritative.
Channel
Submit through support@xiaoyuelabs.com or the on-site inquiry form.
Response target
Receipt is acknowledged within two business days; remediation timing is confirmed after reproduction and scope review.
Scope
Free support covers download integrity, documentation errors, and reproducible Skill defects; project adaptation, managed operation, and ongoing maintenance are separate services.
Release notes
- Added a complete shared-Linux-host deployment workflow covering remote identity, capacity inventory, multi-project isolation, reproducible artifacts, Compose, reverse proxy and TLS, migrations, secrets, verification, and rollback.
- Made before/after health of neighboring applications and recovery headroom required evidence instead of treating the new container's startup as deployment completion.
- Added a secret-safe deployment manifest validator plus a deterministic before/after service-health comparator.
Install & verify
Available for evaluation, not yet packaged
This workflow is listed so its scope, permissions, and service fit can be evaluated. It has not entered the first downloadable release batch and no public artifact exists.