restruo
Self-hosted dashboard for all your Portainer instances with one-click repull + redeploy per stack, image digest-based update detection, red-dot alerts for down/unhealthy containers, and unused-image cleanup.
Ficha actualizada 22 sept 2026, 21:23 · upstream 22 sept 2026, 21:03 · release sin release detectada
Qué es restruo
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
Restruo is a self-hosted dashboard that aggregates every Portainer instance you own into a single list. It replaces the tedious per-stack ritual of logging in, opening each stack, finding the Editor, updating the stack, repulling the image, and redeploying — all on one screen.
It tells you exactly what needs updating by comparing the digest of the image your container is actually running against the registry, so it only flags images behind. Pinned tags (like postgres:16) are deliberately left alone since they represent a deliberate choice rather than drift. The dashboard also shows containers that aren't part of any stack and alerts you on stopped or failing healthchecks.
It installs as a web app with a 30-day session, so it can be added to your phone's home screen and reopens automatically when signed in. Instances are managed from the dashboard without requiring config files or restarts.
- Monitor all your Portainer instances from one dashboard
- Automate stack updates by repulling images and redeploying via API
- Detect containers that have stopped or failed healthchecks with red-dot alerts
- Clean up unused images left behind after image pulls without recreating containers
- Keep track of which Portainer instances are actually running versus stopped
- Send email notifications when updates are detected on any instance
- Updates only compare digests of floating tags (latest, lts, stable, release, edge), leaving pinned versions untouched
- Shows containers that aren't part of a stack so you can manage them independently
- Runs as an unprivileged user (uid 1000) to minimize attack surface on the host
- Supports anonymous registry access for Docker Hub and ghcr.io without credentials
- Provides SMTP email notifications grouped by instance with a test-email feature
- Includes a helper container that runs Portainer/agent updates independently of agents
- Only works with Portainer 2.x (Community Edition) — not supported for Enterprise or Pro versions
- Update notifications require SMTP configuration and may be blocked by corporate firewalls
- The helper container used during agent swaps is unauthenticated and cannot be logged into
- Image digest comparison requires the image to have a digest available in the registry (local builds are not compared)
- Cannot recreate containers that were explicitly stopped — only new images can be pulled
- No support for OAuth/SSO authentication or multi-tenant environments
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy as a Portainer stack by pasting the compose file into Stacks → Add stack, or run `docker compose up -d`. Set `DASHBOARD_PASSWORD` to your dashboard login password. For Gmail, use an App Password with SMTP settings (port 587, STARTTLS). The volume `restruo-data:/data` persists instances across restarts. To add a new instance: go to Instances → Add and enter the Portainer username/password or API token from that instance's admin panel.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.