dcp

Deploy a project to a VPS, commit changes, and push to the remote repository.

Updated Sep 2, 2024
One-click install
npx skills add https://github.com/hdonovan42/H --skill dcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcp
Source: https://github.com/hdonovan42/H/tree/main/.claude/skills/dcp
Command: npx skills add https://github.com/hdonovan42/H --skill dcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys the current project to a VPS, automates the commit of changes, and pushes to the remote repository, reducing manual steps and potential errors in release workflows.

Core Features & Use Cases

  • Detects the target project from context or an explicit argument
  • Executes the project's deploy script to provision or update services
  • Commits updated code and pushes to the remote repository to maintain a clean release history
  • Performs optional health checks to verify deployment success and provides hooks for changelog updates

Quick Start

Run the Deploy, Commit & Push workflow for the current project to deploy to VPS, commit changes, and push to the remote repository.

Frequently Asked Questions about dcp

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

FAQPage Schema
How do I automate git commit and push after deploying to a VPS?

You can automate VPS deployment, git commit, and push end-to-end by executing a project's deploy script, which provisions services and then commits changes to maintain a clean release history on the remote repository.

Do I need a custom deploy script to automate deployment to my VPS?

Yes, automating deployment requires an existing deploy script located under the projects/<NAME>/deploy directory to provision or update your services on the VPS before committing changes.

Can I run health checks to verify my VPS deployment was successful?

Yes, the automated deployment workflow performs optional health checks after executing the deploy script to verify that the VPS deployment succeeded and provides hooks for changelog updates.

What is the best way to manage end-to-end release cycles for local code changes?

The best way to manage end-to-end release cycles is to automate the entire workflow, detecting the target project from context, deploying to the VPS, committing updated code, and safely pushing to the remote repository.

Does this deployment automation work with git workflows for projects like VAULT or AXIOM_v2?

Yes, this deployment automation applies to projects with existing deploy scripts and git workflows, such as VAULT and AXIOM_v2, enabling complete release cycles from local changes to live services.

Why do I need safe and authenticated push operations for automated deployment?

Safe and authenticated push operations are required during automated deployment to securely commit updated code and push changes to the remote repository, preventing potential errors in release workflows.