coracle/flotilla
1
6
Fork 24
Code Issues 42 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Respect custom platform logo env var (VITE_PLATFORM_LOGO is currently ignored) #115

New Issue
Closed
opened 2026-04-02 09:57:25 +00:00 by nayan9617 · 0 comments
nayan9617 commented 2026-04-02 09:57:25 +00:00
Contributor
Copy Link
Copy Source

Hi @hodlbod,

Reason behind the issue:
The docs and env template say we can customise the app logo with VITE_PLATFORM_LOGO, but runtime currently always builds the logo as PLATFORM_URL + /logo.png in state.ts.
That means custom deployments cannot actually use their own logo even though configuration suggests they can.

Approach:
Use VITE_PLATFORM_LOGO when provided, and keep the current behaviour as fallback.

Proposed logic:
PLATFORM_LOGO = import.meta.env.VITE_PLATFORM_LOGO || PLATFORM_URL + /logo.png

Why this is safe:
It is fully backward compatible.
If VITE_PLATFORM_LOGO is not set, behaviour remains exactly the same as today.

Impact:
Custom-hosted/community builds can brand the app correctly.
Removes mismatch between documentation and runtime behaviour.

Validation:
Set VITE_PLATFORM_LOGO in local env and confirm logo is used in places that consume PLATFORM_LOGO

Hi @hodlbod, Reason behind the issue: The docs and env template say we can customise the app logo with VITE_PLATFORM_LOGO, but runtime currently always builds the logo as PLATFORM_URL + /logo.png in state.ts. That means custom deployments cannot actually use their own logo even though configuration suggests they can. Approach: Use VITE_PLATFORM_LOGO when provided, and keep the current behaviour as fallback. Proposed logic: PLATFORM_LOGO = import.meta.env.VITE_PLATFORM_LOGO || PLATFORM_URL + /logo.png Why this is safe: It is fully backward compatible. If VITE_PLATFORM_LOGO is not set, behaviour remains exactly the same as today. Impact: Custom-hosted/community builds can brand the app correctly. Removes mismatch between documentation and runtime behaviour. Validation: Set VITE_PLATFORM_LOGO in local env and confirm logo is used in places that consume PLATFORM_LOGO
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#115
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?