Setup — Frappe Bench (Docker)
Scopo
Descrivere come il bench Frappe viene creato e usato nei container di development e server.
Prerequisiti
.envconfigurato; Docker attivo.- Conoscere docker-architecture.
Development — servizi e porte
| Service | Porta host tipica | Immagine |
|---|---|---|
| frappe | 8001 HTTP, 9001 SocketIO | build deploy/docker/Dockerfile.dev |
| mariadb | 3307 | mariadb:11.8 |
| redis | 6380 | redis:8.8-alpine |
Procedura — primo avvio
bash
make setup
make upL’entrypoint tipicamente:
bench initsu branchversion-16- Symlink/montaggio app
ez_factoryosdaapps/ bench new-site factory.localbench install-app ez_factoryos
Comandi successivi:
bash
make migrate
./scripts/bench-exec.sh bench --site factory.local console
./scripts/bench-exec.sh bench --site factory.local run-tests --app ez_factoryosStaging / Production
Stack multi-servizio: deploy/compose/server.stack.yml.
Il servizio configurator esegue migrate e sync asset prima di backend/workers. Immagine immutabile da GHCR.
Verifica
bash
./scripts/bench-exec.sh bench version
./scripts/bench-exec.sh bench --site factory.local list-appsAtteso: Frappe 16, app ez_factoryos installata.
Troubleshooting
- Bench corrotto in dev: backup +
CONFIRM_RESET=yes EZ_ENV=development make reset. - Upgrade 15→16: operations/upgrade-frappe-v16.
