Community Wishlist Survey 2022/Ability to change wiki subdomain without a phabricator task
From Miraheze Meta, Miraheze's central coordination wiki
You are viewing a proposal made for the Community Wishlist Survey for 2022. |
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
- Unfortunately, due to the sensitive nature of database actions, we will have to decline this request. Because database names are typically the same as the subdomain, we can't implement a system of allowing for custom subdomains either. Apologies but thank you for the request! Agent Isai Talk to me! 06:11, 20 December 2021 (UTC)
Status: Declined
Proposed by Anpang
Proposal summary: Make changing wiki subdomain possible
Full proposal: It's sometimes annoying that a phabricator task is required to change the wiki subdomain. Suggestion is to add a new textbox to ManageWiki which can be used to change the wiki subdomain (and database name of course).
Support[edit | edit source]
Neutral[edit | edit source]
Oppose[edit | edit source]
- While I get the idea behind this request, the reality is that wiki subdomains aren't meant to be changed frequently. As well, changing a wiki subdomain is a very back-end, technical operation, as it involves changing the wiki database name, which incurs its own set of challenges. For example, users can run into login issues initially when a wiki's subdomain is changed. As another example, CentralAuth and related extensions aren't really designed to deal with wiki database name changes, so if a wiki had opted out of Global Sysops, for example, that isn't reflected in the applicable WikiSet, until the wiki advises Stewards that their database name has been changed or a Steward is particularly proactive. As another example, if various wikis have local interwiki links set up to a wiki's former subdomain, those would all break until they've been updated. As a final example, any user rights interwiki changes done on Meta Wiki for a specific wiki will not be carry over to the new database name. Dmehus (talk) 05:08, 20 December 2021 (UTC)
- Maybe a cooldown (and maybe SRE approval) could do it? Anpang📨 05:10, 20 December 2021 (UTC)
- What do you mean by a "cooldown"? As for SRE approval, currently not all SRE team members can change a wiki's subdomain, as it requires running a script that makes certain changes to the database name, updating certain database tables, etc. So only SRE team members designated as either Site Reliability Engineer (Infrastructure) or Engineering Manager have the necessary access. Currently that means John, Reception123, Paladox, and Void. Dmehus (talk) 05:13, 20 December 2021 (UTC)
- Maybe a cooldown (and maybe SRE approval) could do it? Anpang📨 05:10, 20 December 2021 (UTC)
- Strongest oppose 3 YellowFrogger (✉ Talk ✐ Edits) 05:47, 20 December 2021 (UTC)
- It says don't vote until 3 january. Anpang📨 05:49, 20 December 2021 (UTC)
- so close now and reopen by January 3rd. I will not withdraw my vote now YellowFrogger (✉ Talk ✐ Edits) 05:57, 20 December 2021 (UTC)
- It says don't vote until 3 january. Anpang📨 05:49, 20 December 2021 (UTC)
Discussion[edit | edit source]
- The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section