How dennysubke/dennys-umbrel-app-store works
Project type and purpose
• This is not a traditional full-stack web app but an orchestration/catalog repository for community-curated Umbrel “apps.”
• Its purpose is to supply Umbrel with a custom App Store index and per-app Docker compose and Umbrel-app manifest files so community users can install dozens of self-hosted services on their Umbrel node.
File structure
• Top level:
• README.md – describes the store, lists apps, instructions.
• umbrel-app-store.yml – Umbrel manifest for the overall custom App Store UI.
• Many “denny-<appname>/” directories – each contains:
– docker-compose.yml – defines the containers for that app (services, images, volumes, ports).
– data/ (and sometimes config/) – persistent volume mount points for that app.
• Pattern: each app is packaged as its own microservice stack (often a single container + data volume). The store itself is likewise a container that reads the index and displays the UI.
README for additional insights
• The store’s frontend is the Umbrel App Store UI (likely a static or Node.js service defined in umbrel-app-store.yml).
• There is no unified backend code—each app’s docker-compose handles its own service deployment.
• The umbrella “app store” manifest simply points Umbrel at this repo’s index.