erpnext v1.0.2

CI HOW-TO

1. How to add / update new apps (areas to make changes)

CD HOW-TO

1. npm run release / prerelease
2. How to issue various bench commands to the sites

Technical Know-How

1. details about important configs and env variables for CI and CD to use this repo for new

How to get started with the site on local

1. Clone the repo
2. docker compose up
3. docker compose exec -it backend bench --site erpnext.localhost reinstall -y
4. docker compose run migrate

Notes

• Change version in version.txt to build tagged images from the changed version.

Manually Build images

Execute from root of app repo

Clone this repo,

./ci/clone-apps.sh

Set environment variables,

• FRAPPE_VERSION set to use frappe version during building images. Default is version-14.
• ERPNEXT_VERSION set to use erpnext version during building images. Default is version-14.
• VERSION set the tag version. Default is latest.
• REGISTRY_NAME set the registry name. Default is repo name tacten\erpnex-template.
• BACKEND_IMAGE_NAME set worker image name. Default is backend.
• FRONTEND_IMAGE_NAME set nginx image name. Default is nginx.

Build,

docker buildx bake -f docker-bake.hcl --load

Advanced Introduction

• This repo is based on official frappe_docker documentation to build custom apps.
• Fork this repo to build your own image with ERPNext and list of custom Frappe apps.
• Change the frappe and erpnext versions in base_versions.json to use them as base. These values correspond to tags and branch names on the github frappe and erpnext repo. e.g. version-13, v13.25.1
• Change ci/clone-apps.sh script to clone your private and public apps. Read comments in the file to update it as per need.
• Change images/backend.Dockerfile to copy and install required apps with install-app.
• Change images/frontend.Dockerfile to install ERPNext if required.
• Change docker-bake.hcl for builds as per need.
• Workflows from .github/workflows will build latest or tagged images using GitHub.
• Github Actions Runner will build images automatically and publish to container registry.