tools/frappe-crm

Seed copy. This folder is the content of the Forgejo repository tools/frappe-crm (public, like tools/twenty), kept here until the owner creates that repository (amorimdub/idp#116, #121): create it, push these files (with .tekton/) to main, add the Pipelines-as-Code webhook like tools/twenty's, then delete this folder. Flux does not read it.

The image the xupisco platform runs as its Frappe CRM bench (crm-<slug>.xupisco.com): Frappe Framework + the Frappe CRM app, unmodified, at pinned release tags.

Apps	frappe at FRAPPE_BRANCH (Dockerfile), crm at the tag in apps.json
Base	frappe/build + frappe/base (frappe_docker, Debian bookworm), pinned by tag and digest
License	Frappe Framework MIT, Frappe CRM AGPL-3.0. This public repository is the source offer for the running image (AGPL section 13): nothing is patched, the sources are the upstream tags named here
Built by	Tekton via Pipelines-as-Code on every push to main (.tekton/push.yaml), pushed to git.xupisco.com/tools/frappe-crm:main-<unix>-<sha7>
Deployed by	the platform GitOps repo, platform/frappe/ (images: in kustomization.yaml), pinned by digest

Why not the official ghcr.io/frappe/crm image: since frappe_docker reads the app list from a build secret, the CRM repository's workflow (which still passes a build argument) publishes images that contain only frappe (sites/apps.txt of v1.86.0 = frappe). This build is the same images/layered/Containerfile with the app list committed here. The build fails if crm is missing from sites/apps.txt.

Upgrade: bump the CRM tag in apps.json and/or FRAPPE_BRANCH (stay on the Frappe major the CRM tests against: its server-tests.yml), push to main, wait for the build, then pin the new digest in the GitOps repo. The bench pod migrates every site when it starts on a new image.