devops

Manage Docker Compose, cron, Tailscale, and backups for Heimdall deployments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/stanz-stanz/heimdall --skill devops-stanz-stanz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops
Source: https://github.com/stanz-stanz/heimdall/tree/main/.claude/agents/devops
Command: npx skills add https://github.com/stanz-stanz/heimdall --skill devops-stanz-stanz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and automates the infrastructure and operational work required to run Heimdall reliably, removing guesswork when configuring Docker, scheduling scans, maintaining connectivity, and performing migrations.

Core Features & Use Cases

  • Deployment & Configuration: Generate and maintain Docker Compose, environment templates, and system cron entries for Pi and cloud deployments.
  • Monitoring & Recovery: Configure health checks, log rotation, alerting, and operational scripts to diagnose scanner timeouts and resource issues.
  • Migration & Security: Guide encrypted backups, Tailscale setup, secret handling, and a Pi→VPS migration checklist so operators can safely move to Docker-based production.
  • Use Case: An operator migrating Heimdall from a Raspberry Pi to a VPS uses this Skill to produce Dockerfiles, update .env variables, configure Tailscale, schedule cron jobs, and validate health checks before decommissioning the Pi.

Quick Start

Prepare a production Docker Compose deployment by filling the .env template with required keys and running the generated compose file on the target host.

Frequently Asked Questions about devops

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

FAQPage Schema
How do I migrate Docker Compose deployments from a Raspberry Pi to a cloud VPS?

Docker cron health checks verify scheduled scan execution by monitoring cron job outputs, applying log rotation, and triggering alerting mechanisms to diagnose scanner timeouts and resource issues on Pi and cloud deployments.

What is the best way to handle environment-based secrets for Docker orchestration?

Handling environment-based secrets for Docker orchestration requires filling .env templates with required keys and running the generated Docker Compose file on the target host to ensure secure configuration management.

Can I use Tailscale to secure infrastructure with zero inbound ports?

Yes, Tailscale secures infrastructure connectivity by satisfying zero inbound port requirements, allowing operator-driven migrations and routine scans to communicate safely across Pi pilot deployments and cloud VPS environments.

How do encrypted backups work during a Pi to VPS migration?

Encrypted backups during a Pi to VPS migration work by guiding operators through backup encryption procedures and migration validation checklists to safely move Docker-based production data without exposure.

Why does my Docker deployment require zero inbound ports for routine scans?

Docker deployments require zero inbound ports for routine scans to enforce strict network security boundaries, relying on Tailscale for outbound connectivity and secret handling to maintain operational integrity.