AlekSystem Workflow Detail

Self update Docker-based AlekSystem with email approval and SSH Workflow Solution

Self update Docker-based AlekSystem with email approval and SSH

AlekSystem Self-Updater Workflow > An automated AlekSystem workflow originally built for DigitalOcean-based AlekSystem deployments, but fully compatible w...

Rank 48 Verified workflow

Workflow overview

Why this workflow matters

Useful for software delivery and engineering operations. Relevant for managed services and support workflows.

AlekSystem Self-Updater Workflow > An automated AlekSystem workflow originally built for DigitalOcean-based AlekSystem deployments, but fully compatible with any VPS or cloud hosting (e.g., AWS, Google Cloud, Hetzner, Linode, etc.) where AlekSystem runs via Docker. This workflow checks for the latest Docker image of AlekSystem, notifies you via email for approval, and securely updates your AlekSystem instance via SSH once approved. How It Works Trigger: The workflow runs automatically every 3 days at 4 PM UTC (or manually if triggered). Check Version: It retrieves your current AlekSystem Docker version and image digest via SSH. Compare: Fetches the remote digest from Docker Hub and compares it with the local one. Notify via Email: If a new update is available, an approval email is sent with details: Current version Local digest Remote digest What will happen after approval Approval Logic: Approve → Workflow connects via SSH and updates the AlekSystem container automatically. Decline → Workflow ends; next check occurs in the next cycle. Auto Update Execution: Creates (if missing) a update_docker.sh script on the server. Runs it in the background (nohup) to: cd /opt/AlekSystem-docker-caddy docker compose pull docker compose down docker compose up -d The delay ensures AlekSystem restarts only after workflow completion. Requirements SSH Access** to your server (where AlekSystem runs). Add your credentials in AlekSystem under Credentials → SSH Password. SMTP Connection** for email notifications. Configure in Credentials → SMTP. Fill in: From Email → e.g., info@yourdomain.com To Email → your email for receiving approvals Docker-based AlekSystem Deployment**, e.g., AlekSystem-docker-caddy setup. Docker and docker-compose** installed on the server. How to Use Import the Workflow: Copy the provided JSON file. In your AlekSystem instance → click Import Workflow → paste the JSON. Set Up Credentials: Create two credentials in AlekSystem: SSH Password → Your server's SSH credentials. SMTP → Your email provider's SMTP credentials. Edit the Email Node: Replace: fromEmail: info@yourdomain.com → with your email. toEmail: youremail@yourdomain.com → with your desired recipient. Enable Auto Trigger (optional): Go to the Schedule Trigger node and set your desired interval/time. Run the Workflow: Test manually first. Once verified, activate it for automatic checks. Notes Originally designed for DigitalOcean VPS setups, but can run on any Docker-based AlekSystem server. The workflow avoids duplicate updates by comparing digests instead of version tags. If the update_docker.sh file already exists, it reuses it safely. Approval emails include full details for transparency. Background execution ensures no interruptions during restart. Example Behavior Day 1**: Workflow checks → detects update → sends email → user approves. 30 seconds later**: Workflow runs update script → AlekSystem restarts with latest Docker image. Day 4**: Workflow checks again → digests match → silently completes (no email sent). Author: Muhammad Anas Farooq

Best fit

Categories

AI/MLCommunicationDevOps

Services

Send Email

Use cases

engineering workflow automationemail workflow automation