bench setup requirements reads all apps’ pyproject.toml / requirements.txt and installs the Python packages into the bench virtual environment.
Later, when you dynamically create sites via:
docker compose --project-name erpnext-one exec backend \
bench new-site --mariadb-user-host-login-scope=% --db-root-password changeit \
--install-app erpnext --admin-password changeit one.example.com
All dependencies for all apps are already available.
No need to know the site name in advance.
This is fully compatible with the single-server-example.md workflow and supports multiple sites, dynamic app installation, and custom app dependencies.
* build: add pkg-config deb package in build layer
* ci: only use tonistiigi/binfmt for image push
* revert: arm64 builds
* ci: copy build_bench to docker-build-push
* ci: set driver-opts network=host for buildx action
* fix: Add gpg and less
Add gpg so backup "bench --site yoursite.com backup --with-files --compress" does not fail if encryption is enabled
Add "less": fixes#1301
* fix: Add gpg and less
Add gpg so backup "bench --site yoursite.com backup --with-files --compress" does not fail if encryption is enabled
Add "less": fixes frappe#1301
* fix: Update documentation
update documentation to resemble current status
* fix: trailing whitespace
---------
Co-authored-by: Revant Nandgaonkar <revant.one@gmail.com>
* add read perms to nginx-entrypoint
* chore: set file permission for custom image
accepted as per suggestion from users
not required for linux runners
Co-authored-by: Revant Nandgaonkar <revant.one@gmail.com>
