deploy-vps

Deploy GHCR images to a VPS with environment validation and health checks.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/jibaxZZZ/codex-root-configuration --skill deploy-vps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-vps
Source: https://github.com/jibaxZZZ/codex-root-configuration/tree/main/.codex/skills/deploy-vps
Command: npx skills add https://github.com/jibaxZZZ/codex-root-configuration --skill deploy-vps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies deploying a new image to a VPS Ubuntu host by pulling the image from GHCR and running a deploy script to restart services, reducing manual steps and downtime.

Core Features & Use Cases

  • Automated image pull and deploy to a VPS from GHCR.
  • Safe deployment with explicit environment targeting (dev|stage|prd|custom) and placeholder handling for secrets.
  • Built-in rollback readiness and health-check verification.

Quick Start

Specify target environment and image tag, then trigger the deploy script on the VPS to pull and restart the updated image.

Frequently Asked Questions about deploy-vps

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

FAQPage Schema
How do I automate VPS image deployment safely from GHCR?

Automating VPS image deployment from GHCR involves pulling the new image tag and running a deploy script to restart services, enforcing explicit environment validation, secret placeholder handling, and health-check verification before traffic is routed to the updated container.

What's the best way to roll back a failed deployment on a VPS?

Rolling back a failed VPS deployment requires built-in rollback readiness, which ensures the previous working image is preserved and the deploy script can revert service configurations and restart containers to restore the prior environment state safely.

Can I use this VPS deployment approach for dev, stage, and production environments?

Yes, this deployment approach supports dev, stage, and production environments by enforcing explicit environment validation, ensuring that GitOps-style automated image updates target the correct infrastructure with the appropriate safety checks and secret placeholder handling.

How do GitOps workflows handle automated image updates on Ubuntu VPS hosts?

GitOps workflows handle Ubuntu VPS image updates by pulling the latest tag from GHCR and executing a deploy script that restarts running services, reducing manual steps and downtime while ensuring health-check verification passes before completing the rollout.

Why does my automated deployment require health-check verification and secret placeholders?

Automated deployment requires health-check verification to confirm the new image is running correctly before finalizing the rollout, while secret placeholders prevent sensitive credentials from being exposed during the GitOps-style image pull and service restart process on the VPS.