pm2-process-management

Manage PM2 process lifecycles using ecosystem.config.cjs configurations.

6|Updated Mar 11, 2026

Search Tags:#devops #deployment #nodejs #process-management #pm2 #ecosystem-config

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill pm2-process-management-open-hax

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm2-process-management
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/pm2-process-management
Command: npx skills add https://github.com/open-hax/opencode-skills --skill pm2-process-management-open-hax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PM2-based process management often requires manual coordination across multiple apps. This Skill enables orchestration of start, stop, restart, and monitoring for PM2 processes using a centralized ecosystem configuration approach.

Core Features & Use Cases

Ecosystem-driven control: Define and manage multiple PM2 apps via ecosystem.config.cjs.
Lifecycle management: Start, stop, restart, delete, and view logs and status for all processes.
Development workflow integration: Works with the clobber-based compilation flow to ensure the latest configurations are used.

Quick Start

Compile ecosystems with npx shadow-cljs release clobber and start all processes using pm2 start ecosystem.config.cjs.

Frequently Asked Questions about pm2-process-management

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

FAQPage Schema

How do I manage multiple PM2 processes with an ecosystem config?▼

PM2 process management uses an ecosystem.config.cjs file to centrally define and orchestrate multiple apps. You can start, stop, restart, delete, and monitor all defined processes simultaneously using this single configuration file.

What's the best way to start and stop Node.js apps in production using PM2?▼

Starting and stopping Node.js apps in production is handled by PM2 lifecycle commands applied to an ecosystem.config.cjs file. This approach manages dev, test, and production services concurrently without manual intervention for each app.

Does PM2 ecosystem configuration work with clobber-based deployment workflows?▼

PM2 ecosystem configuration integrates with clobber-based deployment workflows. It requires a compiled ecosystem config and access to the .clobber output to ensure the latest configurations are applied to production services.

How do I view logs and monitor health for multiple PM2 apps?▼

Viewing logs and monitoring health for multiple PM2 apps is done through PM2 status and logs commands. These lifecycle commands operate across all processes defined within your ecosystem.config.cjs file.

What do I need to run PM2 process orchestration for my Node.js project?▼

Running PM2 process orchestration requires a Node.js environment with PM2 installed, a compiled ecosystem.config.cjs file, and access to the .clobber output for production deployment workflows.

Why is manual PM2 coordination across multiple apps a problem?▼

Manual PM2 coordination across multiple apps creates operational overhead and configuration drift. Using an ecosystem.config.cjs file solves this by centralizing lifecycle control for starting, stopping, and monitoring all services.