dosubot[bot] commented on issue #36940:
URL: https://github.com/apache/superset/issues/36940#issuecomment-3717548365

   <!-- Answer -->
   In Superset 6.0.0, the way to permanently change the app icon has changed: 
the old `APP_ICON` and `APP_NAME` config options are deprecated and ignored if 
any theme config is present. Branding is now managed through the theming system 
using `THEME_DEFAULT` and `THEME_DARK` in your `superset_config.py`. To set a 
custom logo, add something like:
   
   ```python
   THEME_DEFAULT = {
       "token": {
           "brandLogoUrl": "/static/assets/images/your_logo.png",  # your logo 
path
           "brandLogoAlt": "Your App Name",                        # alt text
           # ...other theme tokens...
       }
   }
   THEME_DARK = {
       "token": {
           "brandLogoUrl": "/static/assets/images/your_dark_logo.png",
           # ...other tokens...
       }
   }
   ```
   [Reference](https://github.com/apache/superset/issues/34824)
   
   For the loading icon (spinner), there is no theme token for it. It's a 
static asset bundled by the frontend build. To change it permanently, replace 
the source image (e.g., `loading.gif`) in 
`superset-frontend/src/assets/images/` with your custom version, then rebuild 
the frontend with the appropriate npm build command. Do not replace files 
directly in `superset/static/assets/images`—these get overwritten on every 
build or deployment due to the asset pipeline and content hashing. 
[Reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/webpack.config.js#L42-L451)
   
   Important: Superset 6.0.0+ requires Node 20.x for frontend builds. Using 
Node 16 or 18 can cause build failures or missing assets, which may prevent 
your customizations from appearing. 
[Reference](https://github.com/apache/superset/issues/34577)
   
   After updating assets and rebuilding, clear your browser cache and 
localStorage to see the changes, especially if you've used the Theme Editor 
before.
   
   If you are running in a multi-tenant or advanced deployment, make sure the 
database is migrated and theme seeding is complete, as themes are now also 
synced to the database. 
[Reference](https://github.com/apache/superset/pull/34679)
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/79177d63-cd6e-457f-9292-fcb030f781ed?feedback_type=other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=In%20Superset%206.0.0%2C%20the%20way%20to%20permanently%20change%20the%20app%20icon%20has%20changed%3A%20the%20old%20%60APP_ICON%60%20and%20%60APP_NAME%60%20config%20options%20are%20deprecated%20and%20ignored%20if%20any%20theme%20config%20is%20present.%20Branding%20is%20now%20managed%20through%20the%20theming%20system%20using%20%60THEME_DEFAULT%60%20and%20%60THEME_DARK%60%20in%20your%20%60superset_config.py%60.%20To%20set%20a%20custom%20logo%2C%20add%20something%20like%3A%0A%0A%60%60%60python%0ATHEME_DEFAULT%20%3D%20%7B%0A%20%20%20%20%22token%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22brandLogoUrl%22%3A%20%22/static/assets/images/your_logo.png%22%2C%20%20%23%20your%20logo%20path%0A%20%20%20%20%20%20%20%20%22brandLogoAlt%22%3A%20%22Your%20App%20Name%2
 
2%2C%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%23%20alt%20text%0A%20%20%20%20%20%20%20%20%23%20...other%20theme%20tokens...%0A%20%20%20%20%7D%0A%7D%0ATHEME_DARK%20%3D%20%7B%0A%20%20%20%20%22token%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22brandLogoUrl%22%3A%20%22/static/assets/images/your_dark_logo.png%22%2C%0A%20%20%20%20%20%20%20%20%23%20...other%20tokens...%0A%20%20%20%20%7D%0A%7D%0A%60%60%60%0A%5BReference%5D%28https%3A//github.com/apache/superset/issues/34824%29%0A%0AFor%20the%20loading%20icon%20%28spinner%29%2C%20there%20is%20no%20theme%20token%20for%20it.%20It%27s%20a%20static%20asset%20bundled%20by%20the%20frontend%20build.%20To%20change%20it%20permanently%2C%20replace%20the%20source%20image%20%28e.g.%2C%20%60loading.gif%60%29%20in%20%60superset-frontend/src/assets/images/%60%20with%20your%20custom%20version%2C%20then%20rebuild%20the%20frontend%20with%20the%20appropriate%20npm%20build%20command.%20Do%20not%20replace%20files%20directly%20in%20%60su
 
perset/static/assets/images%60%E2%80%94these%20get%20overwritten%20on%20every%20build%20or%20deployment%20due%20to%20the%20asset%20pipeline%20and%20content%20hashing.%20%5BReference%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/webpack.config.js%23L42-L451%29%0A%0AImportant%3A%20Superset%206.0.0%2B%20requires%20Node%2020.x%20for%20frontend%20builds.%20Using%20Node%2016%20or%2018%20can%20cause%20build%20failures%20or%20missing%20assets%2C%20which%20may%20prevent%20your%20customizations%20from%20appearing.%20%5BReference%5D%28https%3A//github.com/apache/superset/issues/34577%29%0A%0AAfter%20updating%20assets%20and%20rebuilding%2C%20clear%20your%20browser%20cache%20and%20localStorage%20to%20see%20the%20changes%2C%20especially%20if%20you%27ve%20used%20the%20Theme%20Editor%20before.%0A%0AIf%20you%20are%20running%20in%20a%20multi-tenant%20or%20advanced%20deployment%2C%20make%20sure%20the%20database%20is%20migrated%20and%20theme%2
 
0seeding%20is%20complete%2C%20as%20themes%20are%20now%20also%20synced%20to%20the%20database.%20%5BReference%5D%28https%3A//github.com/apache/superset/pull/34679%29)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36940)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to