hotplex-update

Update the HotPlex gateway binary with build, stop, replace, restart, and validation steps.

47|15|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/hrygo/hotplex --skill hotplex-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotplex-update
Source: https://github.com/hrygo/hotplex/tree/main/.agents/skills/hotplex-update
Command: npx skills add https://github.com/hrygo/hotplex --skill hotplex-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the risk and downtime of updating the HotPlex binary while the service is running, including common failures like “Text file busy”, broken startups, and lack of a fast rollback path.

Core Features & Use Cases

  • End-to-end binary update workflow: Build, verify the new binary, stop the service, replace the executable, restart, and validate health via status and logs.
  • Error handling for deployment failures: Handles stop/replace/start sequencing and common issues with waiting and log-based verification.
  • Rollback mechanism: Restores a previous binary (from backup or rebuild) and verifies that the service returns to a clean, running state.

Use case: After running make build or a git pull, deploy the newly built HotPlex binary to your local machine and ensure the gateway starts cleanly again, or automatically recover if the new version fails to boot.

Quick Start

Tell the assistant: "Update hotplex and restart the service with rollback if it fails."

Frequently Asked Questions about hotplex-update

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

FAQPage Schema
How do I safely update a running binary without getting a Text file busy error?

To avoid a "Text file busy" error during a binary update, you must stop the running service before replacing the executable file. Orchestrating the stop, replace, and restart sequence prevents file lock conflicts.

What is the best way to roll back a failed service deployment?

The best way to roll back a failed service deployment is to restore a previously working binary from backup and restart the service. Verifying service health through status checks and logs ensures the system returns to a clean, running state.

How do I verify service health after a binary update and restart?

To verify service health after a binary update and restart, you should check the service status and inspect the logs. Timestamp verification and log-based health checks confirm the new version has booted cleanly and is operating correctly.

Does this deployment workflow support both system-level and user-level service managers?

Yes, this deployment workflow supports both system-level and user-level service managers. It applies to post-build installs, git pull upgrades, and service recovery scenarios across different service management configurations.

Why do I need to stop the service before replacing the gateway binary during an upgrade?

You need to stop the service before replacing the gateway binary to prevent broken startups and file lock issues. Stopping the service ensures the executable can be safely overwritten and restarted without corruption.