Keep your self-hosted services updated with one workflow
A developer hosts his own services on a Hetzner server. After asking Codex to update n8n a dozen times, he built an n8n workflow that pulls the fresh Docker image and restarts it. Now Codex builds a flow for each new service that checks for updates, applies them and sends a change summary on Telegram. One parent flow runs them all in sequence. He calls it the bare minimum, but self-hosting remains a real security risk.
Done with n8nModerate
What was done
A developer hosts his own services on a Hetzner server. After asking Codex to update n8n a dozen times, he built an n8n workflow that pulls the fresh Docker image and restarts it. Now Codex builds a flow for each new service that checks for updates, applies them and sends a change summary on Telegram. One parent flow runs them all in sequence. He calls it the bare minimum, but self-hosting remains a real security risk.
How to do it
- Paste the prompt into the tool, and replace the text in brackets with your own.
- Read the answer through. Do not send, delete or publish anything until you have seen it yourself.
- Check the original before you trust a figure, a name or a date.
Try it with n8n
Create an n8n workflow for each service I host myself. Each flow should check for a new version, update the service and send me a short change summary on Telegram. Bundle the flows into one parent flow that runs them in sequence. Show me the flows and which services they touch before anything is changed on the server. You are done when the parent flow has run once without errors and I have one summary per service.
Austin Hutchison on his blog ·