| Nikerabbit | |
| Mar 18 2020, 3:38 PM |
| F31699118: image.png | |
| Mar 23 2020, 4:15 PM |
| F31699114: image.png | |
| Mar 23 2020, 4:15 PM |
For last sanity check, and in case "manual" debugging is needed, it would be helpful to access the site using the code that is about to be deployed, before it's actually deployed to everyone.
I just did it on the fly using an x symlink, but should explore using different domain, a cookie or a browser header (last one is used by wikimedia debug).
Change 581624 had a related patch set uploaded (by Nikerabbit; owner: Nikerabbit):
[translatewiki@master] Implement "canary" support using cookie
This is an iteration of the hacky solution I had to implement for debugging. I went for a cookie based solution, since cookies are easier to change in the browser than HTTP headers. Also, this version is transparent in terms of paths, everything looks the same to the browser. This means that everything keeps working because MediaWiki keeps rewriting all links to the canonical version. Also no risk of wrong URL getting cached somewhere.
Possible follow-ups:
Change 582787 had a related patch set uploaded (by Nikerabbit; owner: Nikerabbit):
[translatewiki@master] Replace "this is not production site" warning with canary warning
Possible follow-ups:
- Have visual indication that canary mode is enabled, and/or
| Vector | Timeless |
 |  |
Change 581624 merged by jenkins-bot:
[translatewiki@master] Implement "canary" support using cookie
Change 582787 merged by jenkins-bot:
[translatewiki@master] Replace "this is not production site" warning with canary warning
This has been documented in https://translatewiki.net/wiki/MediaWiki_deployment#How_to_test_code_changes_before_deploying
This is waiting for the documentation to be reviewed. After that this task can be considered done.