Zum Inhalt springen
NEUFehler-Doktor und Wachturm: fehlgeschlagene n8n-Läufe in einfachen Worten erklärt und Ihnen gemailt. Neuigkeiten ansehen

Bibliothek / Code, Git & Entwicklertools

Code, Git & Entwicklertools

n8n-Docker-Container per SSH über eine API bereitstellen

Wenn eine API-Anfrage eingeht, validiert es die Server-Domain und führt SSH-Befehle aus, um einen n8n-Docker-Container bereitzustellen, zu starten, zu stoppen oder zu prüfen.

Was sie bewirkt

# puq-docker-n8n-deploy ## Overview Automated workflow: puq-docker-n8n-deploy. This workflow integrates 9 different services: webhook, stickyNote, code, switch, set. It contains 40 nodes and follows best practices for error handling and security. ## Workflow Details - Total Nodes: 40 - Node Types: 9 - Error Handling: ✅ Implemented - Security: ✅ Hardened (no sensitive data) - Documentation: ✅ Complete ## Node Breakdown - If Node: if - Parametrs: set - API: webhook - 422-Invalid server domain: respondToWebhook - Code1: code - SSH: ssh - Container Actions: switch - Service Actions: switch - Container Stats: switch - API answer: respondToWebhook - ... and 30 more nodes ## Usage Instructions 1. Configure Credentials: Set up all required API keys and credentials 2. Update Variables: Replace any placeholder values with actual data 3. Test Workflow: Run in test mode to verify functionality 4. Deploy: Activate the workflow for production use ## Security Notes - All sensitive data has been removed or replaced with placeholders - Error handling is implemented for reliability - Follow security best practices when configuring credentials ## Troubleshooting - Check error logs if workflow fails - Verify all credentials are properly configured - Ensure all required services are accessible

Die Schritte

  1. If Node
  2. Parametrs
  3. API
  4. 422-Invalid server domain
  5. Code1
  6. SSH
  7. Container Actions
  8. Service Actions
  9. Container Stats
  10. API answer
  11. Inspect
  12. Stat
  13. Start
  14. Stop

Insgesamt 61 Schritte.

Ähnliche Automatisierungen