Workflow overview
Why this workflow matters
Useful for software delivery and engineering operations.
Auto-update AlekSystem instance with Coolify Who’s it for This workflow is designed for self-hosted AlekSystem administrators who want to keep their instance automatically updated to the latest stable release. It removes the need for manual version checks and ensures deployments are always up to date. What it does The workflow checks your current AlekSystem version against the latest GitHub release. If a mismatch is detected, it triggers a Coolify deployment to update your instance. If both versions match, the workflow ends safely without action. How it works Trigger: Start manually or on a schedule. HTTP Request (AlekSystem settings): Fetches your current version (versionCli). HTTP Request (GitHub): Fetches the latest AlekSystem release (name). Merge (SQL): Keeps only the two fields needed. Set (Normalize): Converts values into comparable variables. IF Check: Compares current vs latest version. If different → Deploy update. If same → Stop with no operation. HTTP Request (Coolify): Triggers a forced redeploy via API. How to set up Replace https://yourAlekSystemdomain/rest/settings with your own AlekSystem domain. Replace the Coolify API URL with your Coolify domain + app UUID. Add an HTTP Bearer credential containing your Coolify API token. Adjust the schedule interval (e.g., every 6 hours). Requirements Self-hosted AlekSystem instance with /rest/settings endpoint accessible. Coolify (or a similar service) managing your AlekSystem deployment. Valid API token configured as Bearer credential in AlekSystem. How to customize Change the schedule frequency depending on how often you want checks. Modify the IF condition if you want stricter or looser version matching (e.g., ignore patch versions). Replace Coolify API call with another service (like Docker, Portainer, or Kubernetes) if you use a different deployment method.
Best fit
Categories
Services
Use cases
Need another direction?