Document how plugins can add a custom favicon

[create-issue-branch]

closes #140

[nhoening]

I tested this locally with our current customer's plugin.

Before merging, lets' wait for #151 to land, so we can check if the generated documentation looks nice.

[Flix6x]

Looks clear to me.

[Flix6x]

Actually, I may have run into a problem: I noticed that by overriding the static folder, any plugin logic that uses content from the original flexmeasures static folder flexmeasures/ui/static no longer has access to that content (in my case, the app failed to retrieve daterange-utils.js and flexmeasures.js). Copying what you need to the plugin's static folder is one way to resolve that, but maybe there is a more elegant way that let's the app access both static folders?

[nhoening]

Good catch, this needs a little tinkering with an own static path and/or url for the blueprint: https://www.siparker.net/python/how-to-use-blueprint-static-folders-correctly-in-python-flask/

[Flix6x]

If we leave this one line out (see 61a0b08), both static folders (of the app and of the plugin) seem to be served on the app's static url path. Then there is no need anymore to copy over static content from the app to the plugin.

[nhoening]

So you checked that the favicon still is served? The documentation below should then talk about "path", not "paths". Am 19. Juli 2021 14:38:46 MESZ schrieb Felix Claessen ***@***.***>:

…

If we leave this one line out (see 61a0b08), both static folders (of the app and of the plugin) seem to be served on the app's static url path. Then there is no need anymore to copy over static content from the app to the plugin. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #152 (comment)

-- Gesendet von /e/ Mail.

[Flix6x]

Indeed the favicon is still being served (I checked with a fresh favicon).