Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Ability to Specify CMS Logo in config #1064

Closed
angrybrad opened this issue Jan 31, 2017 · 6 comments
Closed

Ability to Specify CMS Logo in config #1064

angrybrad opened this issue Jan 31, 2017 · 6 comments
Labels
enhancement improvements to existing features

Comments

@angrybrad
Copy link
Member

Created by: Nathaniel Hammond (nathanielhammond@gmail.com) on 2015/03/23 15:31:39 +0000
Votes at time of UserVoice import: 4


A config variable to be able to define the logo in General Settings.

@mattandrews
Copy link

I could do with this. We deploy Craft via a blue/green strategy (eg. spin up new instances from source and then swap over to them), meaning any logo I upload via the control panel gets wiped out between deploys.

@brandonkelly
Copy link
Member

Why not just commit the logo to Git and have it be part of the deploy?

@mattandrews
Copy link

Makes sense – is there a reference in the database somewhere to the filename Craft expects? I can see a path like /cpresources/4139eb4d/logo.svg?v=1548755111 being used, would it be safe to just hardcode a file at this path (or symlink one there) inside my repo?

@brandonkelly
Copy link
Member

As long as there is a file in storage/rebrand/logo/, Craft will show it on the login page. No DB changes necessary.

@mattandrews
Copy link

Excellent! Thank you so much Brandon.

@brandonkelly brandonkelly added enhancement improvements to existing features and removed feature labels Mar 5, 2019
@FreekVR
Copy link

FreekVR commented Mar 31, 2020

I still think it would be nice to be able to set this to a custom path -- or an environment variable. That way it's easy to have a different logo for local/test/staging/production for example as an indicator to users.

@craftcms craftcms locked and limited conversation to collaborators Jul 13, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement improvements to existing features
Projects
None yet
Development

No branches or pull requests

4 participants