Quick question: what does it take for a JS script to be allowed to interact with a toolforge tool?
When I run something like this, I get a Cross-Origin Request Blocked error in the console:
On Tue, Apr 14, 2020 at 6:40 AM billinghurst billinghurstwiki@gmail.com wrote:
Checking our interwiki map, we have the following:
wmflabs
- guc https://tools.wmflabs.org/guc/?user=$1
- gucprefix
https://tools.wmflabs.org/guc/?isPrefixPattern=1&src=rc&user=$1
- luxo https://tools.wmflabs.org/guc/?user=$1
- petscan https://petscan.wmflabs.org/?psid=$1
- quarry https://quarry.wmflabs.org/$1
- stewardry https://tools.wmflabs.org/meta/stewardry/?wiki=$1
- toolforge -> https://tools.wmflabs.org/$1
- toollabs -> https://tools.wmflabs.org/$1
- utrs https://utrs.wmflabs.org/appeal.php?id=$1
- wmfdashboard https://outreachdashboard.wmflabs.org/$1
Toolserver
- jira https://jira.toolserver.org/browse/$1
- tools -> //toolserver.org/$1
Please let us know what it is you want done with these, and for when you would like that scheduled. Thanks.
To also note that we should probably look to update https://www.mediawiki.org/wiki/Toolserver:Main_Page which lovingly still has the interwiki tswiki: :-)
-- billinghurst
------ Original Message ------ From: "Arturo Borrero Gonzalez" aborrero@wikimedia.org To: Cloud-announce@lists.wikimedia.org Cc: "Cloud Services administration and infrastructure discussion" < cloud-admin@lists.wikimedia.org>; "Wikimedia Cloud Services general discussion and support" cloud@lists.wikimedia.org Sent: 13/04/2020 9:25:22 PM Subject: [Cloud] Toolforge: new domain toolforge.org
Hi!
We are happy to announce the new domain 'toolforge.org' is now ready to be adopted by our Toolforge community.
There is a lot of information related to this change in a wikitech page we have for this:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
The most important change you will see happening is a new domain/scheme for Toolforge-hosted webservices:
- from https://tools.wmflabs.org/<toolname>/
- to https://<toolname>.toolforge.org/
A live example of this change can be found in our internal openstack-browser webservice tool:
- legacy URL: https://tools.wmflabs.org/openstack-browser/
- new URL: https://openstack-browser.toolforge.org
This domain change is something we have been working on for months previous to this announcement. Part of our work has been to ensure we have a smooth transition from the old domain (and URL scheme) to the new canonical one. However, we acknowledge the ride might be bumpy for some folks, due to technical challenges or cases we didn't consider when planning this migration. Please reach out intermediately if you find any limitation or failure anywhere related to this change. The wikitech page also contains a section with information for common problems.
You can check now if your webservice needs any specific change by creating a temporal redirection to the new canonical URL:
$ webservice --canonical --backend=kubernetes start [..] $ webservice --canonical --backend=gridengine start [..]
The --canonical switch will create a temporal redirect that you can turn on/off. Please use this to check how your webservice behaves with the new domain/URL scheme. If you start the webservice without --canonical, the temporal redirect will be removed.
We aim to introduce permanent redirects for the legacy URLs on 2020-06-15. We expect to keep serving legacy URLs forever, by means of redirections to the new URLs. More information on the redirections can also be found in the wikitech page.
The toolforge.org domain is finally here! <3
-- Arturo Borrero Gonzalez SRE / Wikimedia Cloud Services Wikimedia Foundation
Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud
Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud