Logo Endpoint

[NotSpecial]

Several tools we are using allow branding in form of a logo provided by URL.

Examples:

• ReDoc used by the API itself
• Portainer (cluster management)
• Wiki

So far we always need some workarounds to actually host the logo somewhere, e.g. portainer uses a direct URL to a image uploaded to the wiki.

As it's always nice to make a good appearance, the logo should be more reliably accessible,
thus I propose an endpoint '/logo/' for the API, which can serve the different variants of our logo (with/without text etc.)

[cburchert]

I feel like this is not really a good use of the API, as this content is completely static. If this is really just about Logos, then we should just host a simple HTTP Server like static.amiv.ethz.ch and put stuff there in plain.

[NotSpecial]

I see your point, however we do not really have any static content aside from the logo.

The API needs the logo anyway (e.g. for the OAuth login page or the docs), so why not put it on a static endpoint where others can access it as well?

I like the idea that at least the API is self-contained, so using an external server just for a logo seems to me like unnecessary overcomplicating issues.

[NotSpecial]

Update: in #325, I now moved the logo we need for OAuth and (soon) the online docs to a static folder served by flask.

However, the discussion in this issue remains:

• Should we keep it like this and only serve the logo used by the API itself.
• Do we want a solution that serves different formats of the logo?
• Do we want to switch to an external host for the logo?