Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customize the logo / Change the name of Overseerr #404

Open
Dabu-dot opened this issue Dec 19, 2020 · 80 comments · Fixed by #825
Open

Customize the logo / Change the name of Overseerr #404

Dabu-dot opened this issue Dec 19, 2020 · 80 comments · Fixed by #825

Comments

@Dabu-dot
Copy link
Contributor

Is your feature request related to a problem? Please describe.
One of the simpliest way to customize Ombi as a User nowadays is to replace the Logo and Name of the application (showing up in the tab next to the favicon). I would be nice if the admin could do that in Overseerr as well.

Describe the solution you'd like
Within the "General Settings" Section, create a subsection named "Customization" (or else) to upload a .png or .jpg for the new logo that will overwrite the existing one. Same thing could be done for a text input where you could write a new name for the application and rename Overseerr.

@Dabu-dot Dabu-dot changed the title Customize the logo of Overseerr / Change the name of the application Customize the logo / Change the name of Overseerr Dec 19, 2020
@ctrlaltd1337ed

This comment has been minimized.

@cyb3rgh05t

This comment has been minimized.

@Albeyon

This comment has been minimized.

@morganzero

This comment has been minimized.

@WoisWoi

This comment has been minimized.

@github-actions

This comment has been minimized.

@Cajs

This comment has been minimized.

@Emalton

This comment has been minimized.

@PhAzE-Variance

This comment has been minimized.

@TheCatLady

This comment has been minimized.

@stale

This comment has been minimized.

@stale stale bot added the stale label Jun 11, 2021
@Dabu-dot

This comment has been minimized.

@stale stale bot removed the stale label Jun 11, 2021
@carnivorouz

This comment has been minimized.

@KJThaDon

This comment was marked as spam.

@Emalton
Copy link

Emalton commented Feb 27, 2023

@TheCatLady Would this issue be suitable for the never-stale label?

@KJThaDon
Copy link

I would also like to mention that the "custom application title" update from v.1.19 doesn't change the Overseerr name displayed when a user attempts to login via the plex auth screen. I believe the expected behavior would also change the application title name on the login screen. image

Anyone know of a fix for this?

@cavfeet

This comment was marked as off-topic.

@carnivorouz

This comment was marked as off-topic.

@remserwis
Copy link

I've got logo_full.svg (for top left corner) and logo_stacked.svg (for login screen) working properly with docker folder mapping. Great stuff....Unfortunately emails still coming with original instead of putting logo_full.png the same way on server. Name of the file in email is correct...I am on 1.32.5 version....Do you think it's hard linked now on sending bot ?

@CyberSparkCloud
Copy link

I've got logo_full.svg (for top left corner) and logo_stacked.svg (for login screen) working properly with docker folder mapping. Great stuff....Unfortunately emails still coming with original instead of putting logo_full.png the same way on server. Name of the file in email is correct...I am on 1.32.5 version....Do you think it's hard linked now on sending bot ?

Hi @remserwis . How did you get it working in docker folder mapping? I've tried mapping a svg file using docker-compose to /app/overseerr/public/logo_full.png and /app/public/logo.png but neither seem to change the default logo.

@robbbbbie
Copy link

I've got logo_full.svg (for top left corner) and logo_stacked.svg (for login screen) working properly with docker folder mapping. Great stuff....Unfortunately emails still coming with original instead of putting logo_full.png the same way on server. Name of the file in email is correct...I am on 1.32.5 version....Do you think it's hard linked now on sending bot ?

Hi @remserwis . How did you get it working in docker folder mapping? I've tried mapping a svg file using docker-compose to /app/overseerr/public/logo_full.png and /app/public/logo.png but neither seem to change the default logo.

Using Docker, I mapped /MY_FILE_DIRECTORY/public to /app/public as well as /MY_FILE_DIRECTORY/public/logo_full.svg to /app/public/logo_full.svg. This is using my custom logo_full.svg for the top left corner, as well as using other my other custom logo files in the public directory such as logo_stacked.svg for the login screen and favicon.ico, favicon-16x16.png, and favicon-32x32.png for my custom favicon. I implemented this about a year ago and it has been working well ever since.

If you did something similar to this with a logo_full.png and it's not working, maybe you need to include a logo_full.svg file as well. I believe the .svg and .png files are used for different use cases, so if you don't have a .svg file you probably need one as well. Otherwise you could try mapping your .png file to the .svg file, but I'm not sure that would work as I haven't tried it myself.

@CyberSparkCloud
Copy link

CyberSparkCloud commented Mar 27, 2023

Thanks for getting back to me. When I wrote .png in my previous reply I did mean .svg. I hadn't tried mapping the folder to public though as well as the file. However I've just tried that but still no joy.. I can live without the custom logo but thanks anyway.

 volumes:
  - /var/docker/overseerr/config:/config
  - /var/docker/overseerr/config:/app/public
  - /var/docker/overseerr/config/logo_full.svg:/app/public/logo_full.svg

@robbbbbie
Copy link

I see you mapped all overseer directories to one local config directory. I also noticed you didn't specify overseer's /app directory on your config mapping. For reference, I separated them out into similarly named local directories. This was how I mapped the volumes on my container:

volumes:
  - /var/docker/overseerr/config:/app/config
  - /var/docker/overseerr/public:/app/public
  - /var/docker/overseerr/public/logo_full.svg:/app/public/logo_full.svg
  - /var/docker/overseerr/src:/app/src

@remserwis
Copy link

Hi...I wanted to send you a screenshot from portainer, but it looks since I just updated tautulli docker my mappings are gone. I will redo them and paste a picture later. I remember it didn't want to work with mapping of the folder for me...I mapped file2file for logos.

@CyberSparkCloud
Copy link

cheers guys. I was using the docker-compose example from the overseerr website which only mentions a config folder
https://docs.overseerr.dev/getting-started/installation#:~:text=Docker%20Compose-,For,-details%20on%20how

I've just added the folders / mapping exactly as you did but still no joy. I also tried mapping a svg file directly to /app/public/logo.svg and /app/overseerr/public/logo_full.svg (with only my previous config folder) and the logo then disappears from Overseerr which feels like progress. I've tried multiple svg files of varying resolutions.

I'm on the latest image 1.32.5.

@remserwis
Copy link

if logo disappeared, it's probably a good sign that you did correct mapping. now just create proper svg. From my experience:

  1. I downloaded original logo end edited it to mine (to keep size etc. the same)
  2. when exporting there was a setting about logo positioning ( my soft was centering it by default but it should be in top left corner )

@robbbbbie
Copy link

I was having the same issue last year, and found a fix soon after.

The issue was the resolution of the .svg file. The resolution I was initially using was rendering as 0px x 0px, so it was mapped correctly, just not rendering at the desired size. I edited my .svg file to have a width of 300 and a height of 92 and that rendered properly for me. You might need to toy around with the height and width variables to get it just right for your file's dimensions, but editing that should resolve your issue.

@CyberSparkCloud
Copy link

Cheers guys. Seems like the resolution of the svg may be the key. I got it working using 300 x 92 svg and the below container mappings.
volumes:
- /var/docker/overseerr/config:/config
- /var/docker/overseerr/config/logo_full.svg:/app/public/logo_full.svg

I tried to change the logo on the login screen by mapping a svg file the same size as the original stacked svg file (332 x 165) but couldn't get this logo to change. I tried mapping this using the below:
- /var/docker/overseerr/config/logo_stacked.svg:/app/public/logo_stacked.svg

I also tried changing the logo in the email by using a png file as recommended in a post above but couldn't get this to work either.
I think I will call it a day, I got 1 out of 3 changed and spent a lot longer on this than I planned to!

@Jmcguire525
Copy link

I wish this would get implemented in an easy to use way... I don't know how to code it but if I hired someone to do that and submit a PR would it be accepted?

@AIndoria
Copy link

AIndoria commented Jun 9, 2023

What absurdity that most of the comments are marked as spam or offtopic. Devs should be better than this. People sometimes want to have fun names for their instances.

@SpartacusIam
Copy link

What absurdity that most of the comments are marked as spam or offtopic. Devs should be better than this. People sometimes want to have fun names for their instances.

Because it's very clear that not only do the devs have no interest in implementing this change, they are obviously against it.

@adamk33n3r
Copy link

What absurdity that most of the comments are marked as spam or offtopic. Devs should be better than this. People sometimes want to have fun names for their instances.

Because it's very clear that not only do the devs have no interest in implementing this change, they are obviously against it.

If they are against it, they should close this issue then.

@SpartacusIam
Copy link

What absurdity that most of the comments are marked as spam or offtopic. Devs should be better than this. People sometimes want to have fun names for their instances.

Because it's very clear that not only do the devs have no interest in implementing this change, they are obviously against it.

If they are against it, they should close this issue then.

Well, if they were okay with it being publicly known that they are against it, then yes this thread would have been closed a long time ago and comments wouldn't be continuously being marked as spam. Clearly they don't want their users to know that they are against their users using any kind of custom branding. I guess is they feel like they're branding is what promotes their software. But I really don't see that as being the case.

@adamk33n3r
Copy link

What absurdity that most of the comments are marked as spam or offtopic. Devs should be better than this. People sometimes want to have fun names for their instances.

Because it's very clear that not only do the devs have no interest in implementing this change, they are obviously against it.

If they are against it, they should close this issue then.

Well, if they were okay with it being publicly known that they are against it, then yes this thread would have been closed a long time ago and comments wouldn't be continuously being marked as spam. Clearly they don't want their users to know that they are against their users using any kind of custom branding. I guess is they feel like they're branding is what promotes their software. But I really don't see that as being the case.

Ya, it's not like the people that are using my instance of Overseer are EVER going to set up their own 😂 that's why they're using mine! So not sure who they'd be marketing to

@JoshMout

This comment was marked as abuse.

@sct
Copy link
Owner

sct commented Jul 25, 2023

We mark comments as off-topic because they are. Constantly asking for a feature doesn't make us more aware of it. We work in our free time. We are aware of the ticket and want to support it eventually. It's just not the top priority right now.

@Kevin1Smid
Copy link

Kevin1Smid commented Aug 1, 2023

For those who want a temporary fix, in NGINX just set:
location /logo_full.svg {
proxy_pass youractuallogo.svg;
}

@morganzero
Copy link

morganzero commented Aug 1, 2023

To customize the project logos, follow these steps:

Locate the default logos in the project code under the following paths:

        /public/logo_full.png
        /public/logo_full.svg
        /public/logo_stacked.svg
        /public/os_logo_filled.svg
        /public/overseerr_poster_not_found_logo_top.svg
        /public/overseerr_poster_not_found_logo_center.svg

If you're using Docker and building the container, ensure that the public folder is copied to /app/overseerr/public.

To deploy the project using docker-compose, bind your custom logo files to the application by adding this line to your docker-compose.yml file:

volumes:
  - "/path/to/your/custom/logos/:/app/overseerr/public"

The docker-compose example would look like this instead:

---
version: "3"
  overseerr:
    image: sctx/overseerr:latest
    restart: unless-stopped
    ports:
      - 5055:5055
    volumes:
      - "/path/to/your/custom/logos/:/app/overseerr/public"
      - "/opt/appdata/overseerr:/app/config"

Replace "/path/to/your/custom/logos/" with the path to your custom logo files.
Replace "/opt/appdata/overseerr" with the desired path for your config data.

Rename your custom logos with the following exact names to replace the defaults:

        logo_full.png
        logo_full.svg
        logo_stacked.svg
        os_logo_filled.svg
        overseerr_poster_not_found_logo_top.svg
        overseerr_poster_not_found_logo_center.svg

By following these steps, you can easily customize the logos for the project.

TL;DR:
To deploy using docker-compose, follow the example above, and ensure your custom logos are placed in the correct path within the project.

Alt Text

@xcybermanx
Copy link

I would also like to mention that the "custom application title" update from v.1.19 doesn't change the Overseerr name displayed when a user attempts to login via the plex auth screen. I believe the expected behavior would also change the application title name on the login screen. image

Anyone know of a fix for this?

have you know how change it ?

@kalyway101
Copy link

For anyone who is finding some conflicting information in previous versions/comments... the current location that logos are pulled from is /app/public/. It no longer is pulling from /app/overseerr/public as of version 1.33.2.

@jordanjones98
Copy link
Contributor

jordanjones98 commented Mar 13, 2024

I have a branch on my fork that allows you to change the text but not the logo. I still need to clean up the CSS to make it work better with longer names, but I will PR it soon.

I do have a PR open for the name of the application on the plex login page #3811

@almulder
Copy link

I have a branch on my fork that allows you to change the text but not the logo. I still need to clean up the CSS to make it work better with longer names, but I will PR it soon.

I do have a PR open for the name of the application on the plex login page #3811

Man this will be nice to have done, (Also hopefully changes the name in emails to "Open Server Name")

For images I did what a user did above (for Unraid).

And I Would love to test the name change

@ldejavul
Copy link

I've got logo_full.svg (for top left corner) and logo_stacked.svg (for login screen) working properly with docker folder mapping. Great stuff....Unfortunately emails still coming with original instead of putting logo_full.png the same way on server. Name of the file in email is correct...I am on 1.32.5 version....Do you think it's hard linked now on sending bot ?

In case anyone finds this troubleshooting your email logo change. Clear the cache for your domain. I spent a stupid amount of time wondering why my full_logo.png wasn't changing in emails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.