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

Staging website needs favicon different from production #2136

Closed
dwvanstone opened this issue Nov 7, 2016 · 20 comments
Closed

Staging website needs favicon different from production #2136

dwvanstone opened this issue Nov 7, 2016 · 20 comments
Assignees
Milestone

Comments

@dwvanstone
Copy link
Contributor

The dev website has a favicon that differs from production. It would be beneficial to have the staging website also have a different favicon from production - it could even match the dev site if need be.

@irilyth
Copy link

irilyth commented Nov 7, 2016 via email

@AdmiralJota
Copy link
Contributor

Wouldn't blue make it the same as prod?

My first suggestion would be "take the current prod icon and make it grayscale". But my second suggestion would be "make the staging icon the same as dev". Both of those would require a minimal amount of image manipulation work.

@irilyth
Copy link

irilyth commented Nov 7, 2016 via email

@irilyth
Copy link

irilyth commented Nov 7, 2016 via email

@irilyth
Copy link

irilyth commented Apr 30, 2017

I think prod is currently black, not blue... If it's secretly a very dark blue, maybe staging could be a light blue?

Huh, check that out, it totally is blue.

Light blue for staging? Orange? I don't have a preference, but would like to do something, so I can keep my tabs straight. :^)

@blackshadowshade
Copy link
Contributor

What about no favicon for the moment? I can certainly rename the favicon to another name as a temporary measure.

@cgolubi1
Copy link
Contributor

I'd like to veto making manual changes to files installed by vagrant on deployed sites. It messes up the deployment process and wastes time.

@cgolubi1
Copy link
Contributor

To suggest an answer to the actual question: is there any reason not to use the dev favicon for the staging site as well?

@blackshadowshade
Copy link
Contributor

Since we're now using staging for the same purpose as our old dev, I think this would be fine.

@irilyth
Copy link

irilyth commented Apr 30, 2017

I'd said

We talked about this briefly on IRC, and liked the idea of it being different from both dev and prod

I don't recall the details, and am lazy. I think it'd be nice if the mini-dev sites used the dev icon, which I think they don't at the moment.

In any case, here's two yellow versions, as possible staging options:

favicon_staging_1

favicon_staging_2

The first is the prod one with the colors rotated and lightened; the second replaces the "BM" with the darker red from the main site.

If folks like either, I'll put in a PR. If folks have other suggestions, lemme know, keeping in mind that I'm not very good at this. :^)

@irilyth
Copy link

irilyth commented Apr 30, 2017

To clarify slightly, I think that blue for prod, yellow (or something) for staging, and red for mini-dev, would be better than using red for both staging and mini-dev.

@cgolubi1
Copy link
Contributor

cgolubi1 commented Apr 30, 2017

IMO the second one irilyth suggested is just fine; i don't think the bar is high for the graphics on this, and i think it's recognizeably a BM icon.

@blackshadowshade
Copy link
Contributor

If I remember correctly, this requires a change to the database and the UI also?

@irilyth
Copy link

irilyth commented Apr 30, 2017

Jota seems to have done a bunch of stuff related to the dev favicon in #849, but some of it looks like infrastructure to distinguish the dev and prod sites in general, so I'm not sure what exactly needs to be done to add a third option.

@AdmiralJota
Copy link
Contributor

AdmiralJota commented Apr 30, 2017

If you want to set the site up to be able to recognize staging as separate from dev and prod, then I believe there are two code files you'll want to change: Login.js and Overview.js. I've created a gist containing changes that I think should work: https://gist.github.com/AdmiralJota/1dd4f2e734f4c395ec9f1ea9894df2af

(I also updated the link to Cheapass Games, since it looks like our URL for their BM page is out of date. [EDIT: and fixed a typo where we had "you\r" instead of "you're".])

If those two files (and the icon itself) get checked into the main branch, then you should be able to configure the site to be staging by updating the Config.js file; I believe that @cgolubi1's deployment process already has a clause for doing this when pushing to dev.

@cgolubi1 cgolubi1 self-assigned this Apr 30, 2017
@cgolubi1
Copy link
Contributor

cgolubi1 commented Apr 30, 2017

Okay. So do we think the many-dev-sites should use the dev site icon? I think they should. Anyone disagree?

[Edit: i've gone ahead and made this so, because it's a change in my scripts that setup the many-dev-sites, not in the codebase. But if anyone does object, let me know.]

@blackshadowshade
Copy link
Contributor

Sounds fine to me.

@blackshadowshade
Copy link
Contributor

@AdmiralJota, when I get a free moment today, if Chaos hasn't already done it, I'll put up a pull request with the new URL and the typo change.

@irilyth
Copy link

irilyth commented Apr 30, 2017 via email

@cgolubi1
Copy link
Contributor

Oops, sorry for the miss there. Thanks, shadowshade.

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

No branches or pull requests

5 participants