Home

SwarmCLI

Deploy to multiple Docker Swarm servers from one repo — no config drift, no rollback scripts, no CI boilerplate.

  Your Repo ──→ SwarmCLI ──→ ┌─ dev-server   (17 stacks)
                              ├─ prod-server  (18 stacks)
                              └─ db-server    (1 stack)

The Problem

You manage several Docker Swarm servers — dev, staging, prod, maybe a dedicated database host. Each one has its own configs, scattered across repos or maintained by hand. Deploying means writing 50+ lines of CI pipeline per stack, copy-pasting docker stack deploy with slight variations. Rollback? A hand-written script you hope still works. Secrets live in .env files shared over Slack.

SwarmCLI exists to make all of this a single command.

What You Get

• One-command deploy — swarmcli deploy my-stack sends the right config to the right server
• Instant rollback — swarmcli rollback my-stack restores the previous version
• Profile-based isolation — one repo, different settings per server
• Minimal CI config — one CLI call instead of 50 lines of pipeline YAML
• Docker-familiar commands — ls, ps, logs, deploy
• Secure secrets — Docker Secrets & Configs, synced automatically before deploy
• Per-stack isolation — each stack owns its repos and data
• JSON output — --json for automation, webhooks, monitoring

Before vs After

Without SwarmCLI	With SwarmCLI
Separate configs per server	Single repo, profile-based isolation
docker stack deploy + manual steps	swarmcli deploy my-stack
Custom rollback scripts	swarmcli rollback my-stack
SSH + docker service logs	swarmcli logs my-stack --service api
50+ lines of CI config per stack	One CLI call, minimal pipeline config
Secrets in env files or manual sync	swarmcli secret sync + Docker Secrets

How It Works

1. Create a profile        →  One per server (dev, prod, db)
2. Define stacks           →  Apps with services, variables, secrets
3. swarmcli deploy <stack> →  Syncs repos → builds images → deploys
4. swarmcli ps <stack>     →  Verify everything is running
5. swarmcli rollback       →  Something wrong? One command to undo

Who Is It For

Role	How you use it
DevOps	Set up profiles, CI/CD pipelines, manage secrets
Backend dev	Deploy your services, check logs, rollback
Frontend dev	Deploy, check service status
QA	Deploy feature branches for testing

Quick Start

# Install
git clone https://github.com/KoninMikhail/swarmcli.git /opt/swarmcli && cd /opt/swarmcli
./install.sh

# Create your first profile from the example
cp -r examples/profiles/example-server profiles/my-server

# Select the profile
swarmcli use my-server

# Deploy a stack
swarmcli deploy core-backend

# Check status
swarmcli ps core-backend

# Something wrong? Rollback instantly
swarmcli rollback core-backend

→ See Quick-Start for the full walkthrough.

Documentation

Getting Started

• Requirements — system requirements
• Installation — install and configure
• Quick-Start — first deploy in 5 minutes

Concepts

• Glossary — terms and definitions
• Profiles — server profiles and isolation
• Stacks — application stacks
• Services — service types (git, registry, none)
• Deploy-Flow — what happens on deploy

Guides

• Create-Profile — create a server profile
• Create-Stack — create an application stack
• Deployment-Guide — deploy, monitor, manage
• Rollback — revert to previous version
• Secrets-Management — secure secret handling
• Jinja2-Templating — template-based stack configs
• Resource-Management — CPU/Memory management
• CI-CD-Integration — GitLab CI / GitHub Actions

Reference

• CLI-Reference — all commands and flags
• Configuration-Files — YAML file formats
• Environment-Variables — all environment variables

Operations

• Troubleshooting — common issues and solutions

Developer Documentation

For architecture details, ADRs, and internals — see docs/ in the main repository.

SwarmCLI vs Alternatives

	SwarmCLI	Raw Docker CLI	Portainer	Kubernetes
Profile isolation	Built-in	Manual	No	Namespaces
One-command deploy	Yes	Multiple steps	GUI-based	Helm
Built-in rollback	Yes	Manual	Limited	Yes
CI/CD integration	Native	DIY	Webhooks	DIY
Secrets management	Built-in	Manual	GUI	Built-in
Jinja2 templating	Built-in	No	No	Helm templates
Learning curve	Low	Low	Medium	High
Setup complexity	Minimal	Minimal	Medium	High

Project Info

• Platform: Linux (Ubuntu 20.04+, Debian 11+, CentOS 8+)
• Written in: Bash + Python
• License: MIT
• GitHub Repository
• Changelog
• Contributing