enterprise-demo-deploy

Upgrade live enterprise demo deployments with pg_dump backups and rollback safeguards.

Updated May 3, 2026
One-click install
npx skills add https://github.com/miethe/boxbrain-2 --skill enterprise-demo-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-demo-deploy
Source: https://github.com/miethe/boxbrain-2/tree/main/.claude/skills/enterprise-demo-deploy
Command: npx skills add https://github.com/miethe/boxbrain-2 --skill enterprise-demo-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents risky, incomplete, or hard-to-recover in-place upgrades of the live enterprise demo box by enforcing release validation, database backups, migration audits, deployment isolation, and authenticated verification.

Core Features & Use Cases

  • Pre-flight Gating: Confirms the target release is on main, audits migration changes, and checks environment-validator requirements before connecting to the server.
  • Safe Deployment and Rollback: Creates database and environment backups, applies the release with the correct Compose project, and directs recovery through a documented database restore when migrations or startup fail.
  • Post-Deploy Verification: Checks health, version, OpenAPI path coverage, Alembic heads, logs, authenticated application behavior, and Backstage isolation.
  • Use Case: Use it when promoting a tagged release to the shared demo EC2 instance while protecting existing data and ensuring the deployed enterprise surface is fully operational.

Quick Start

Use the enterprise demo deploy skill to audit, back up, deploy, and verify release v0.55.1 on the live demo box.

Frequently Asked Questions about enterprise-demo-deploy

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

FAQPage Schema
How do I safely deploy a tagged release to a live EC2 instance using Docker Compose?

To safely deploy a tagged release to an EC2 instance, enforce release provenance checks on the main branch, create a pg_dump database backup, apply the Docker Compose deployment, and run authenticated post-deploy smoke tests to verify service availability.

What is the best way to prevent data loss during an in-place database migration on a shared demo box?

Preventing data loss during an in-place database migration requires creating a pg_dump backup before applying changes, auditing forward-only Alembic migration heads, and directing recovery through a documented database restore if startup fails.

How do I verify service availability after upgrading a Docker Compose deployment?

Verify service availability after upgrading by checking health endpoints, confirming version numbers, inspecting OpenAPI path coverage, validating Alembic heads, reviewing application logs, and testing authenticated application behavior.

Can I use this deployment process if my target release is not tagged on the main branch?

No, this deployment process enforces pre-flight gating that confirms the target release is tagged on the main branch before proceeding, ensuring release provenance and preventing unsafe upgrades to the live demo box.

What should I do when a database migration fails during an in-place upgrade on EC2?

When a database migration fails during an in-place upgrade, direct your recovery through a documented database restore using the pg_dump backup created during pre-flight to preserve existing data and service availability.

Do I need to run environment validation before connecting to the server for a Docker Compose deployment?

Yes, you need to run environment validation to check environment-validator requirements and audit migration changes during pre-flight gating before connecting to the server for a Docker Compose deployment.