Twenty CRM for the xupisco platform: the official image plus a one-line change of the workspace limit (AGPL-3.0, source offered here)
This repository has been archived on 2026-10-03. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
  • Dockerfile 100%
Find a file
2026-09-30 00:20:40 +00:00
.tekton Twenty with the workspace limit raised (AGPL source offer), built by Tekton 2026-09-29 22:50:12 +00:00
.ci-trigger ci: trigger the first image build (amorimdub/idp#45) 2026-09-30 00:02:02 +00:00
Dockerfile Dockerfile: check only compiled .js for the old limit (source maps keep the original source) 2026-09-30 00:20:40 +00:00
README.md Twenty with the workspace limit raised (AGPL source offer), built by Tekton 2026-09-29 22:50:12 +00:00
renovate.json Twenty with the workspace limit raised (AGPL source offer), built by Tekton 2026-09-29 22:50:12 +00:00

tools/twenty

The image the xupisco platform runs as its CRM (crm.xupisco.com): the official Twenty release with one modification.

Upstream twentycrm/twenty, pinned by tag and digest in the Dockerfile (source: the same tag in twentyhq/twenty)
Modification MAX_WORKSPACES_WITHOUT_ENTERPRISE_KEY 5 -> 1000 in the compiled server (packages/twenty-server/src/engine/core-modules/auth/constants/max-workspaces-without-organization-key.constants.ts)
License AGPL-3.0 (upstream's). This repository is the source offer for the modified server (AGPL section 13)
Built by Tekton via Pipelines-as-Code on every push to main (.tekton/push.yaml), pushed to git.xupisco.com/tools/twenty:main-<unix>-<sha7>
Deployed by the platform GitOps repo, platform/twenty/, pinned by digest

The build fails when the constant is renamed or moved (the grep guards in the Dockerfile), so an upgrade never ships an unpatched server unnoticed. Twenty's ee/ code, licensing and paid features are untouched: this does not unlock any Enterprise feature other than the number of workspaces.

Upgrade: bump the tag and digest of the FROM line together, push to main, wait for the build, then bump the digest in the GitOps repo. Renovate proposes the first step.