lord

Deploys Docker apps to serversGitHub with automatic failover and recovery for deployed apps and manages them centrally from one place.

1|Updated Sep 5, 2024
One-click install
npx skills add https://github.com/schmidthole/lord --skill lord
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lord
Source: https://github.com/schmidthole/lord/tree/main/.claude/skills/lord
Command: npx skills add https://github.com/schmidthole/lord --skill lord

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert guidance on using lord, a minimalist PaaS CLI tool for deploying Docker containers to remote servers via SSH, reducing complexity and manual steps in container hosting.

Core Features & Use Cases

  • Deploy multiple standalone containers to remote hosts with automatic Traefik-based HTTPS routing.
  • Choose between direct container transfer (load) or registry-based deployment, streamlining CI/CD workflows.
  • Manage deployment lifecycle from local machine or CI/CD, including status, logs, and server health checks.

Quick Start

Ensure a lord.yml file is present in your project and Docker is installed locally. Then run lord -deploy from your project root to build and deploy to the configured remote server; use lord -init to create a starter lord.yml if needed.

Frequently Asked Questions about lord

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

FAQPage Schema
How do I deploy Docker containers to a remote server via SSH?

Deploy Docker containers to a remote server via SSH by running the lord CLI from your project root after configuring a lord.yml file, which automates the build and transfer process to your target host.

How does Traefik-based HTTPS routing work for remote Docker deployments?

Traefik-based HTTPS routing is automatically configured when deploying standalone containers to remote hosts, routing external web traffic securely to your deployed Docker containers without manual reverse proxy setup.

Do I need a Docker registry to deploy containers remotely?

You do not need a Docker registry to deploy containers remotely, as the system supports direct container transfer via SSH load operations, though registry-based deployment workflows are also available for CI/CD pipelines.

What do I need to set up before deploying containers with a minimalist PaaS CLI?

Before deploying containers, you need Docker installed on both local and remote machines, SSH access configured to the target servers, and a lord.yml configuration file present in your local project directory.

Can I manage the deployment lifecycle of remote Docker containers from my local machine?

You can manage the remote Docker container deployment lifecycle from your local machine or CI/CD environment, including checking deployment status, viewing container logs, and running server health checks.

What is the best way to deploy multiple standalone containers to a single remote host?

The best way to deploy multiple standalone containers to a single remote host is using a minimalist PaaS CLI with a lord.yml configuration, which automates SSH transfers and configures Traefik routing for each service.