n8n-self-hosting
Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, provision, or deploy n8n on their own server/VPS (Hetzner, DigitalOcean, AWS EC2, bare metal) — single/regular mode or queue mode with workers — or to update, back up, restore, or harden such an instance, or make Python Code nodes run on it (task runners). For SELF-HOSTED n8n (Docker), not n8n Cloud and not building workflows. The skill makes the agent ask single-vs-queue first, collect domain/SSH/timezone inputs, generate fresh secrets on the box, and bring the stack up with TLS. Trigger on "deploy n8n", "self-host n8n", "n8n docker compose", "n8n queue mode / workers", "n8n reverse proxy / SSL", "back up / update my n8n", "Python runner unavailable" / "n8nio/runners sidecar", or "we don't want to give every user the OAuth client secret" / "enable Sign in with Google" (credential overwrites).
Pinned to revision 19cd793f4789, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/n8n-self-hosting/SKILL.md
- skills/n8n-self-hosting/CREDENTIAL_OVERWRITES.md
- skills/n8n-self-hosting/DAY2.md
- skills/n8n-self-hosting/QUEUE_MODE.md
- skills/n8n-self-hosting/README.md
- skills/n8n-self-hosting/SECURITY.md
- skills/n8n-self-hosting/SINGLE_MODE.md
- skills/n8n-self-hosting/TASK_RUNNERS.md
- skills/n8n-self-hosting/assets/.env.queue.example
- skills/n8n-self-hosting/assets/.env.single.example
- skills/n8n-self-hosting/assets/Caddyfile
- skills/n8n-self-hosting/assets/docker-compose.queue.yml
- skills/n8n-self-hosting/assets/docker-compose.single.yml
- skills/n8n-self-hosting/assets/init-data.sh
Every link opens the file at its source, pinned to the revision this page describes.