Skip to content

Conversation

@shreven0
Copy link

What does this PR do?

It allows for an instance administrator to configure a custom logo and favicon in settings.yml

Why is this change important?

This feature has been requested in #3208, and based on the number of thumbs up emojis, is wanted by several people (although I guess it's not that important)

How to test this PR locally?

Set the custom_files.* options in settings.yml

Related issues

Closes #3208

Sorry if there are a lot of issues with this, it's my first ever PR :)

also removed searxng-wordmark from templates directory and build
files, because it is no longer used anywhere
@vojkovic
Copy link
Member

At first glance, this looks like another implementation of #2276. I suppose this PR can reopen the discussion on if this feature is desirable.

@return42 What is your opinion on this?

@return42
Copy link
Member

return42 commented Dec 13, 2024

update: please read this comment


TBH I have lost sight of #2276 .. I'm very sorry .. and thanks for reminding me 👍

I prefer the way #3208 goes, adding favicon and logo to the brand section / we should not open a custom section IMO.

@Bnyro
Copy link
Member

Bnyro commented Dec 18, 2024

In contrast to #2276 I personally prefer this PR here because it allows to set svg icons with a png fallback while #2276 seems to be enforcing the use of .ico, which might have been common in the last century, but not anymore since then.

The specific way of implementation here however is debatable, I agree.

@return42 return42 added new feature New feature or request brand Individualization of an instance in the sense of its brand labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

brand Individualization of an instance in the sense of its brand new feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add options for logo and favicon

4 participants