veda-deploy

Deploys and validates Veda services on production infrastructure with guarded steps.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/VedaAstro/veda-skills --skill veda-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: veda-deploy
Source: https://github.com/VedaAstro/veda-skills/tree/main/veda-deploy
Command: npx skills add https://github.com/VedaAstro/veda-skills --skill veda-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes safe production deployment for Veda services, reducing errors during code transfers, restarts, environment updates, and post-deploy checks.

Core Features & Use Cases

  • Production Deployments: Handles frontend, backend, bot, and websocket releases on the Veda server with the correct deployment flow.
  • Operational Guardrails: Enforces confirmation before deploy, zero-downtime reloads where required, health checks, and safe handling of environment variables.
  • Server Troubleshooting: Guides diagnosis of failing services, PM2 process inspection, rsync synchronization, and recovery from common deployment incidents.
  • Use Case: A developer needs to update app-myveda, verify the active PM2 process, sync build artifacts, and confirm the service is healthy after release.

Quick Start

Use this Skill to prepare, validate, and safely deploy the requested Veda service, then summarize what changed and how to verify it.

Frequently Asked Questions about veda-deploy

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

FAQPage Schema
How do I deploy frontend and backend services to a production server using rsync and PM2?

To deploy services using rsync and PM2, you sync build artifacts to the server, apply environment variables, and restart the PM2 process. This workflow includes rsync exclusions for safe transfers and zero-downtime reloads for minimal disruption.

What is the best way to verify post-deploy health for websocket and bot releases?

Post-deploy health verification checks the active PM2 process and service endpoints after a websocket or bot release. It confirms successful synchronization and validates that the service is responding correctly in the production environment.

How does environment variable handling work during a production deployment?

Environment variable handling during deployment ensures secure configuration updates without exposing secrets. The workflow applies guarded confirmations before injecting environment variables into PM2 processes for frontend, backend, or Docker-based releases.

Can I recover from a failing PM2 process incident without a full service redeployment?

You can recover from failing PM2 process incidents without full redeployment by inspecting PM2 logs and diagnosing the active service. The workflow guides troubleshooting, rsync synchronization fixes, and targeted restarts for incident recovery.

Do I need guarded confirmation for every Docker-based release workflow?

Yes, guarded confirmation is required for Docker-based release workflows to prevent accidental production overwrites. This operational guardrail ensures safe execution of sync operations, restarts, and environment updates before applying changes.