pm-system-deployment

Automate PM System deployment with Docker multi-arch images and tarball handoff.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/freedomw1987/tree_monstor --skill pm-system-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-system-deployment
Source: https://github.com/freedomw1987/tree_monstor/tree/main/skills/devops/pm-system-deployment
Command: npx skills add https://github.com/freedomw1987/tree_monstor --skill pm-system-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the complexity of deploying a full-stack PM System application across different CPU architectures while keeping source code private from clients. It eliminates the guesswork in Docker multi-arch builds, Prisma 7 configuration pitfalls, and production release workflows.

Core Features & Use Cases

  • Multi-architecture Docker images: Build and package backend images for both x86 and ARM servers using a single manifest list.
  • Client release automation: Generate tarballs with checksums, one-line install scripts, and hardened docker-compose files for air-gapped customer deployments.
  • Production hardening: Avoid known Elysia.js, Prisma 7, and Tailwind v4 migration bugs with documented workarounds and verification recipes.

Quick Start

Use the pm-system-deployment skill to build a multi-arch release tarball for version 1.0.0 and verify it loads correctly in a clean Docker environment.

Frequently Asked Questions about pm-system-deployment

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

FAQPage Schema
How do I build Docker multi-arch images for both linux/amd64 and linux/arm64?

Build Docker multi-arch images by creating a single manifest list that packages backend images for both linux/amd64 and linux/arm64, ensuring cross-architecture compatibility across x86 and ARM servers.

What is the best way to deploy a full-stack application to air-gapped on-premise servers?

Deploy to air-gapped on-premise servers by generating client release tarballs containing checksums, idempotent one-line install scripts, and hardened docker-compose files for zero-downtime updates without requiring internet access.

How do I prevent source code exposure when distributing Docker images to clients?

Prevent source code exposure during client distribution by using client-side tarball handoff with pre-built multi-arch Docker images, ensuring the source code stays private while delivering deployable artifacts with checksum verification.

Do I need specific workarounds for Prisma 7 and Elysia.js bugs in production Docker deployments?

Production Docker deployments require documented workarounds for known Elysia.js, Prisma 7, and Tailwind v4 migration bugs, providing verification recipes to avoid configuration pitfalls during release.

How do idempotent install scripts with checksum verification work for client releases?

Idempotent install scripts with checksum verification validate tarball integrity on every run, ensuring repeated client installations produce the same correct state without corrupting existing Docker environments.