Custom branding - Add primary color and app name customization by normanalie · Pull Request #134 · Vito0912/forkmost

normanalie · 2026-04-21T09:18:22Z

This pull request introduces workspace-level branding customization, allowing workspace owners to set a primary theme color and favicon. The changes span both frontend and backend, providing a new settings UI, persisting branding options, and applying them dynamically throughout the app. Additionally, the app name can now be customized via environment variables and is consistently displayed in the UI.

This changes are useful for enterprise use.

Workspace Branding Customization

Added a new WorkspaceBrandingForm component to the workspace settings page, allowing workspace owners to update the primary color and favicon URL for their workspace. These settings are validated and persisted, and only owners are permitted to make changes. [1] [2] [3] [4]
Extended workspace types to include appearance settings (primaryColor, faviconUrl) and ensured these are available on the workspace object. [1] [2] [3]
Implemented the applyWorkspaceBranding utility, which dynamically updates CSS variables and favicon links based on workspace settings, ensuring the UI reflects the selected branding.
Integrated branding application into relevant components and providers to ensure branding is applied on authentication and workspace context changes. [1] [2] [3]

App Name and UI Consistency

Introduced support for customizing the app name via the APP_NAME environment variable, with a fallback to "Forkmost". Updated all relevant UI components to use the new getAppName helper for consistent branding. [1] [2] [3] [4] [5] [6] [7]

Backend Enforcement

Updated the backend workspace controller to enforce that only workspace owners can update branding-related fields (primaryColor, faviconUrl).

Build and Environment Configuration

Updated the Vite configuration and .env.example to support the new APP_NAME environment variable, ensuring it is available at build time. [1] [2]

Code Quality and Formatting

Improved code formatting and imports in several files for better readability and maintainability. [1] [2] [3] [4] [5] [6] [7]

…d favicon

Configure the app name (Default Forkmost) with an env variable.

Vito0912 · 2026-04-21T09:26:54Z

This project is currently EOL.

The PR adds the option for a user to load any URL each time they visit a page. If a favicon option were added, I would require it to be downloaded to the server first and served from there.

Vito0912 · 2026-04-21T09:32:06Z

Thanks for opening this PR!
This looks like a sensible addition.

Currently this projects reaches EOL, but I am not opposed to merge one or two smaller PRs like this one.
I am really concerned about security, thus I don't am very attracted to have the favicon an arbitrary URL.
If there a reason why you need it that way, I am open to discuss this further and then test and review the PR properly

Greetings

For security reasons custom favicon need to be uploaded rather than an URL

normanalie · 2026-04-21T10:24:45Z

Yes, absolutely! I changed the favicon customization to use file upload, reusing AvatarIconType and limiting it to 10 KB. The file is stored locally on the server.

Vito0912

Thank you for the changes!
I left some comments. If you think someone should be the case, please say so.
This is just a first look without actually running it, so maybe I missed some behavior.

Vito0912 · 2026-04-21T10:39:46Z

+
+    preparedFile.fileName = uuid4() + preparedFile.fileExtension;
+    const filePath = `${getAttachmentFolderPath(AttachmentType.WorkspaceFavicon, workspaceId)}/${preparedFile.fileName}`;
+    const faviconUrl = `/api/attachments/favicon/${workspaceId}/${preparedFile.fileName}`;


Can a workspace have multiple favicons?

I think it would make more sense to have it just as favicon.<> or something like this.

You're right, I've copied the same logic as avatars but it's not needed for favicon

Vito0912 · 2026-04-21T10:41:22Z


 type FormValues = z.infer<typeof formSchema>;

+const FAVICON_MAX_SIZE = 100 * 1024; // 100KB


Is there a reason why it is 100KB here, but 10KB on the server side?

Vito0912 · 2026-04-21T10:43:34Z

+    const faviconUrl =
+      (workspace?.settings as any)?.appearance?.faviconUrl ?? null;
+
+    if (faviconUrl && !faviconUrl.toLowerCase().startsWith('http')) {


I know that this is probably because you run the fork for yourself. But as the URL never was introduced I would prefer not to have old handling from before paths

Or do I overlook something and this would have active usage? Also for the other functions?

Introduced in my previous commit, forgot to remove it when we changed from URL to file upload

Vito0912 · 2026-04-21T10:45:28Z

  }

+  @Public()
+  @Get('attachments/favicon/:workspaceId/:fileName')


Same here. I think just having attachments/favicon/:workspaceId would make more sense.
This could have caching "issues" if changed, but as it is not cached that long, it should be not that big of a problem

- Removed legacy code from the first implementation of custom favicon. - Update favicon filenaming for simplicity and update the favicon server url

…gs-for-owner

Vito0912 · 2026-04-27T10:09:02Z

JFYI I will review it next weekend. Sorry for the delay!

Vito0912 · 2026-05-04T10:12:39Z

Sorry, totally forgot. Next weekend. If not by Saturday, please ping me

normanalie added 4 commits April 13, 2026 12:29

feat(workspace): add owner-only branding settings for theme colors an…

46d3cfd

…d favicon

fix(client): apply branding colors to mantine runtime variables

2b60d49

Custom app name

7c1638e

Configure the app name (Default Forkmost) with an env variable.

Create docker_run_postgres.sh

94c2c5a

Vito0912 suggested changes Apr 21, 2026

View reviewed changes

Change favicon custom from URL to file upload

785ee62

For security reasons custom favicon need to be uploaded rather than an URL

Vito0912 reviewed Apr 21, 2026

View reviewed changes

Remove code from URL favicon and update favicon storage

b2ad9dc

- Removed legacy code from the first implementation of custom favicon. - Update favicon filenaming for simplicity and update the favicon server url

normanalie requested a review from Vito0912 April 24, 2026 13:41

Merge branch 'personal' into codex/add-theme-color-and-favicon-settin…

1715be4

…gs-for-owner

Vito0912 approved these changes May 11, 2026

View reviewed changes

Navigation Menu

Repository navigation

Custom branding - Add primary color and app name customization - #134

Custom branding - Add primary color and app name customization#134
normanalie wants to merge 7 commits into
Vito0912:personalfrom
normanalie:codex/add-theme-color-and-favicon-settings-for-owner

normanalie commented Apr 21, 2026

Uh oh!

Vito0912 Apr 21, 2026

Uh oh!

Vito0912 commented Apr 21, 2026

Uh oh!

normanalie commented Apr 21, 2026

Uh oh!

Vito0912 left a comment

Uh oh!

Vito0912 Apr 21, 2026

Uh oh!

normanalie Apr 24, 2026

Uh oh!

Vito0912 Apr 21, 2026

Uh oh!

Vito0912 Apr 21, 2026

Uh oh!

normanalie Apr 24, 2026

Uh oh!

Vito0912 Apr 21, 2026

Uh oh!

Vito0912 commented Apr 27, 2026

Uh oh!

Vito0912 commented May 4, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		type FormValues = z.infer<typeof formSchema>;

		const FAVICON_MAX_SIZE = 100 * 1024; // 100KB

Conversation

normanalie commented Apr 21, 2026

Uh oh!

Vito0912 Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Vito0912 commented Apr 21, 2026

Uh oh!

normanalie commented Apr 21, 2026

Uh oh!

Vito0912 left a comment

Choose a reason for hiding this comment

Uh oh!

Vito0912 Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

normanalie Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Vito0912 Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Vito0912 Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

normanalie Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Vito0912 Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Vito0912 commented Apr 27, 2026

Uh oh!

Vito0912 commented May 4, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants