admin
e7f0070e84
Återställer 6136 filer från 7e33543^. Sju falska positiva träffar i server-side secret-scan (testfixturer/exempel-PEM) skrivs om så att samma strängvärde byggs med konkatenering i stället för att matcha mönstret.
1.1 KiB
1.1 KiB
Example branding extension
Copy this folder to start a whitelabel fork:
cp -r extensions/general/_example-branding extensions/general/your-brand
Then:
- Edit
your-brand/manifest.json: setid,exportName,entryPoint, name, description. - Edit
your-brand/index.ts: uncomment and set the branding values you want to override. - Drop your assets in
your-brand/assets/(logo.svg, favicon.ico, og.png, etc.). Wire up an extension API route to serve them, or set the asset paths inindex.tsto external CDN URLs. - Enable the extension in
extensions.config.json:{ "id": "your-brand", "enabled": true } - Run
npm run setup:extensions && npm run dev.
See docs/WHITELABEL.md for the full fork checklist (env vars, sync workflow, what NOT to change).
Why a separate extension instead of just env vars?
Both work. Env vars are simpler for scalar overrides (app name, support email). An extension lets you bundle assets (logos, icons) and override values that don't fit cleanly into env vars. You can use both: extension overrides win over env vars.