Apps
Templates include compose files, persistent volumes, ports, healthchecks, prebuilt image names, and install notes. Search by name, category, or image.
Images
Each app card lists the exact Dockan images it needs. Releases include `registry/index.tsv` in the Store archive, plus one prebuilt image pack per app. Installs download only the selected app pack when images are not already local.
./dockan-store images APP_ID
./dockan-store images all
DOCKAN_STORE_FORCE_IMAGES=1 ./dockan-store images APP_ID
./dockan-store build-images all
./dockan-store build-images mysql:local
DOCKAN_STORE_ENGINE=docker ./dockan-store build-images mysql:local
./dockan-store export-app-images wordpress
# release assets:
registry/index.tsv
dockan-store-images-APP_ID.tar.gz
How Install Works
For normal use, download `dockan-store.tar.gz` from the latest GitHub Release. It contains the Store templates and image index. App image packs are downloaded on demand, one app at a time, to stay below GitHub's release asset size limit.
curl -L -o dockan-store.tar.gz https://github.com/Dockan-Conteneurisation-libre/Dockan-store/releases/latest/download/dockan-store.tar.gz
tar -xzf dockan-store.tar.gz
cd Dockan-Store
./dockan-store install APP_ID
cd ~/dockan-apps/APP_ID
dockan compose up
dockan compose health
sudo dockan compose autostart -f dockan.yml
# custom target:
./dockan-store install APP_ID /srv/apps/APP_ID
# prepare images only:
./dockan-store images APP_ID
Update Apps
Use `update` when a new Store release ships fresher image packs. It imports the app images again, keeps existing volumes, and redeploys the installed app with its current `dockan.yml`.
./dockan-store update APP_ID
# custom install path:
./dockan-store update APP_ID /srv/apps/APP_ID
# direct Dockan equivalent:
dockan pull IMAGE:local registry
dockan compose redeploy -f /path/to/dockan.yml