Carrying changes across upgrades
Three files make a deployment its own — branding/ in the web repo, config/claimsaccesscontrol.php in the API, and config/sso.php if you run more than one identity provider. All three live inside the upstream repos, so every deployment needs a way to keep its own versions across upgrades. We have not settled on a recommended mechanism: fork-and-rebase, a build-time overlay and a mounted config all work.
What is already fixed, whichever route you take:
branding/ |
claimsaccesscontrol.php |
sso.php |
|
|---|---|---|---|
| Consumed at | Next.js build time | PHP runtime, subject to config cache | PHP runtime, subject to config cache |
| Can be mounted into a running container | No — it is compiled into the bundle | Yes | Yes |
| Needs | A rebuild of the web image | A redeploy, or config:clear |
A redeploy, or config:clear |
| Only needed if | You are rebranding | Your IdP's names differ from the shipped ones | You have more than one IdP |
That asymmetry is the main constraint: any approach that works by mounting files at runtime covers the API but cannot cover web branding.