rhino/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-24 10:49:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

icon cache -> icon service

Stefan Melmuk
2025-06-23 23:45:45 +02:00
parent 21dede8c97
commit 4a934f0b7f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Using-custom-website-icons.md

@@ -9,7 +9,7 @@ If you want to add custom icons for your website entries you can place them in t
![bitwarden-uri-graphic](https://github.com/user-attachments/assets/47bdf0f1-46f9-41af-8030-d0f860e2a056) ![bitwarden-uri-graphic](https://github.com/user-attachments/assets/47bdf0f1-46f9-41af-8030-d0f860e2a056)
This means the scheme and port will be ignored when requesting icons, so you can't provide different icons based on the port number. This means the scheme and port will be ignored when requesting icons, so you can't provide different icons based on the port number.
If you are using the `internal` icon cache (the default) Vaultwarden will generally serve the icons from the `ICON_CACHE_FOLDER`. If you are using the `internal` icon service (the default) Vaultwarden will generally serve the icons from the `ICON_CACHE_FOLDER`.
While the web-vault supports a couple of image types like ICO, BMP, GIF, JPG, WEBP and PNG, the cached icons themselves are always named `<fqdn>.png` or `<IP>.png` (eg. `data/icon_cache/en.wikipedia.org.png`). So you should name your custom icons accordingly. While the web-vault supports a couple of image types like ICO, BMP, GIF, JPG, WEBP and PNG, the cached icons themselves are always named `<fqdn>.png` or `<IP>.png` (eg. `data/icon_cache/en.wikipedia.org.png`). So you should name your custom icons accordingly.