Auto-update Tech namespace pages 2024-09-16 19:02:01.634156

miraheze · Sep 16, 2024 · ee70ba9 · ee70ba9
1 parent 87d335a
commit ee70ba9
Show file tree

Hide file tree

Showing 95 changed files with 350 additions and 152 deletions.
diff --git a/content/tech-docs/Tech:Adding_a_new_extension.md b/content/tech-docs/Tech:Adding_a_new_extension.md
@@ -23,8 +23,10 @@ It should be noted that it is a good idea to add any configuration variable the
 * [Updating an extension](https://meta.miraheze.org/wiki/Tech:Updating_an_extension)
 * [Removing an extension](/tech-docs/techremoving_an_extension)
 
-[Category:Guides](https://meta.miraheze.org/wiki/Category:Guides)
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Guides](https://meta.miraheze.org/wiki/Category:Guides)
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Adding_a_new_extension](https://meta.miraheze.org/wiki/Tech:Adding_a_new_extension)
diff --git a/content/tech-docs/Tech:Appointment_and_revocation_policy.md b/content/tech-docs/Tech:Appointment_and_revocation_policy.md
@@ -59,7 +59,9 @@ If you already have a shell account and want to get extra privileges (or are req
    * Why you need extra access, and what benefit this would provide to either Miraheze or yourself (regarding productivity);
    * What access you specifically need (log viewing, service interaction, ability to deploy changes).
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Appointment_and_revocation_policy](https://meta.miraheze.org/wiki/Tech:Appointment_and_revocation_policy)
diff --git a/content/tech-docs/Tech:CSP_Policy.md b/content/tech-docs/Tech:CSP_Policy.md
@@ -30,7 +30,9 @@ This policy lays out the process by which the [Technology team](/tech-docs/techv
 * This policy applies to all services governed by Miraheze's Privacy Policy. Two resource types are exempted from this policy and can be added by the Technology team: any resource fully controlled by the Technology team (hosted on-premise or outsourced, via contracted vendor) and any resource hosted via a domain name fully owned by Miraheze.
 In the event of a dispute or situation not covered by this policy, the Director of Technology decides.
 
-[Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
+## Categories
+
+* [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:CSP_Policy](https://meta.miraheze.org/wiki/Tech:CSP_Policy)
diff --git a/content/tech-docs/Tech:Compromised_Handling.md b/content/tech-docs/Tech:Compromised_Handling.md
@@ -93,7 +93,10 @@ Under EU law, we're required to notify all European users in the event of a brea
 * If we determine that a decent section of users have had their information compromised, run a sitenotice.  If it happened to be restricted to a few wikis, we can run it there, otherwise, do a global sitenotice.  Link to the incident report.
 * If we can identify individual users who have had their PII compromised, go ahead and email them if they ever gave us their address.  If we have a lot of emails to write (hopefully not), prepare a mass email.  Use the bcc field as to not make things worse.
 * External notification methods should be considered too, like Twitter.
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Compromised_Handling](https://meta.miraheze.org/wiki/Tech:Compromised_Handling)
diff --git a/content/tech-docs/Tech:Conduct_Policy.md b/content/tech-docs/Tech:Conduct_Policy.md
@@ -32,8 +32,10 @@ title: Tech:Conduct Policy
 
 Failure to adhere to this conduct policy may result in disciplinary action, up to and including revocation of access and removal from the team.
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
-[Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+* [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Conduct_Policy](https://meta.miraheze.org/wiki/Tech:Conduct_Policy)
diff --git a/content/tech-docs/Tech:DNS.md b/content/tech-docs/Tech:DNS.md
@@ -22,7 +22,9 @@ Code is deployed automatically through puppet. This allows code to be merged and
 
 The system should be moved to manual at some point, though there is not enough risk to justify this yet.
 
-[Category:Services](https://meta.miraheze.org/wiki/Category:Services)
+## Categories
+
+* [Category:Services](https://meta.miraheze.org/wiki/Category:Services)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:DNS](https://meta.miraheze.org/wiki/Tech:DNS)
diff --git a/content/tech-docs/Tech:Delete_a_wiki.md b/content/tech-docs/Tech:Delete_a_wiki.md
@@ -17,7 +17,9 @@ Performing the deletion if 14 days have **not** passed:
 * Run `mwscript extensions/CreateWiki/deleteWiki.php loginwiki --delete --deletewiki <wiki database>`
 * Drop the database on the relevant database server.
 
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Delete_a_wiki](https://meta.miraheze.org/wiki/Tech:Delete_a_wiki)
diff --git a/content/tech-docs/Tech:Deleting_Echo_notifications.md b/content/tech-docs/Tech:Deleting_Echo_notifications.md
@@ -9,7 +9,9 @@ While quite a rare occurrence, it sometimes happens that a user is left with glo
 * Select the `metawiki` database
 * Run `DELETE FROM echo_unread_wikis WHERE euw_user = '[RESULT FROM PREVIOUS QUERY]' AND euw_wiki = '[desired wiki]';`
 
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Deleting_Echo_notifications](https://meta.miraheze.org/wiki/Tech:Deleting_Echo_notifications)
diff --git a/content/tech-docs/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki.md b/content/tech-docs/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki.md
@@ -12,7 +12,9 @@ To delete or move large batches of pages on a wiki, execute the following comman
 * sudo `sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki=wikidbname -u "Miraheze maintenance script" -r "[[phab:T###|Requested]]" /home/yourshellusername/wikisubdomain.txt`, replacing the ***bolded italicized*** portions as applicable. **Note:** *`deleteBatch.php`* is interchangeable with *`moveBatch.php`* as applicable.
 * Logout (if you are done with your business on `mwtask181`).
 
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki](https://meta.miraheze.org/wiki/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki)
diff --git a/content/tech-docs/Tech:Fixing_slot_roles_and_content_models.md b/content/tech-docs/Tech:Fixing_slot_roles_and_content_models.md
@@ -32,8 +32,10 @@ ALTER TABLE content_models AUTO_INCREMENT = 1;
 ```
 After running that make sure you exit shell.php or sql.php (if using) and rerun or it won't know of the AUTO_INCREMENT being reset and IDs will still be wrong.
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Fixing_slot_roles_and_content_models](https://meta.miraheze.org/wiki/Tech:Fixing_slot_roles_and_content_models)
diff --git a/content/tech-docs/Tech:GHSA.md b/content/tech-docs/Tech:GHSA.md
@@ -77,7 +77,9 @@ If you need to create an advisory, follow the steps below:
 * Low – The attack has some impact on availability, but this is degradation only.
 * High – The attack has some impact on availability, but this is a critical service, or there is a total unavailability of the service.
 
-[Category:Guides for sysadmins](https://meta.miraheze.org/wiki/Category:Guides_for_sysadmins)
+## Categories
+
+* [Category:Guides for sysadmins](https://meta.miraheze.org/wiki/Category:Guides_for_sysadmins)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:GHSA](https://meta.miraheze.org/wiki/Tech:GHSA)
diff --git a/content/tech-docs/Tech:GitHub.md b/content/tech-docs/Tech:GitHub.md
@@ -96,7 +96,9 @@ mediawiki is the repository that manages the MediaWiki source code, skins, and e
 
 ## References 
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:GitHub](https://meta.miraheze.org/wiki/Tech:GitHub)
diff --git a/content/tech-docs/Tech:Grafana.md b/content/tech-docs/Tech:Grafana.md
@@ -12,7 +12,9 @@ All data is collected on a central server which also serves the [web interface](
 
 This is done automatically on the first puppet run as Grafana configuration is handled in the base module. The central server can be replaced by adding `role::grafana` to the server in site.pp.
 
-[Category:Monitoring services](https://meta.miraheze.org/wiki/Category:Monitoring_services)
+## Categories
+
+* [Category:Monitoring services](https://meta.miraheze.org/wiki/Category:Monitoring_services)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Grafana](https://meta.miraheze.org/wiki/Tech:Grafana)
diff --git a/content/tech-docs/Tech:Graylog.md b/content/tech-docs/Tech:Graylog.md
@@ -73,7 +73,9 @@ It is recommended to save this config to a session. Choose a server you would li
 
 Configuring Graylog is a combination of Puppet usage and using the web interface for configuration (where configuration will eventually be stored in MongoDB on graylog161.wikitide.net). [role::graylog](https://github.com/miraheze/puppet/blob/master/modules/role/manifests/graylog.pp) is used for graylog161's configuration. [base::syslog](https://github.com/miraheze/puppet/blob/master/modules/base/manifests/syslog.pp) contains the configuration for every server logging to Graylog.
 
-[Category:Services](https://meta.miraheze.org/wiki/Category:Services)
+## Categories
+
+* [Category:Services](https://meta.miraheze.org/wiki/Category:Services)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Graylog](https://meta.miraheze.org/wiki/Tech:Graylog)
diff --git a/content/tech-docs/Tech:Home.md b/content/tech-docs/Tech:Home.md
@@ -59,7 +59,10 @@ The Technology team strives for transparency. Below are some of our policies and
 * [Procedures in Case of Compromise](/tech-docs/techcompromised_handling)
 * [Security](/tech-docs/techsecurity) ([GHSA](/tech-docs/techghsa))
 * [Conduct Policy](/tech-docs/techconduct_policy)
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Home](https://meta.miraheze.org/wiki/Tech:Home)
diff --git a/content/tech-docs/Tech:Icinga-MediaWiki_Monitoring.md b/content/tech-docs/Tech:Icinga-MediaWiki_Monitoring.md
@@ -64,7 +64,9 @@ This page is used to provide monitoring guidance for MediaWiki-related services
 * *Is an alert a bad thing?* **Yes, if not just a temporary issue that resolves itself, it is a problem.**
 * *If it's warning/critical, how do we fix it?* **The person who requested the custom domain (or other wiki bureaucrats) should be notified and asked to point their domains to us again. If there is no response and/or they fail to do so in a reasonable time (not less than a week) the custom domain and SSL certificate should be removed until the issue is resolved.**
 
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Icinga/MediaWiki_Monitoring](https://meta.miraheze.org/wiki/Tech:Icinga/MediaWiki_Monitoring)
diff --git a/content/tech-docs/Tech:Icinga.md b/content/tech-docs/Tech:Icinga.md
@@ -14,7 +14,9 @@ Icinga is configured as standard out of the box for Debian Bullseye with little
 
 Users can refer to either "Contacts" (those who get emails and alerts) or "Interface users" (those who can use the Icinga interface). Contacts are added through the configuration file [users.conf](https://github.com/miraheze/puppet/blob/master/modules/monitoring/files/users.conf). Interface users can be added by an admin in [https://monitoring.wikitide.net/user/list](https://monitoring.wikitide.net/user/list), then adding their username to the relevant permissions needed in [roles.ini](https://github.com/miraheze/puppet/blob/master/modules/icingaweb2/templates/roles.ini.erb).
 
-[Category:Monitoring services](https://meta.miraheze.org/wiki/Category:Monitoring_services)
+## Categories
+
+* [Category:Monitoring services](https://meta.miraheze.org/wiki/Category:Monitoring_services)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Icinga](https://meta.miraheze.org/wiki/Tech:Icinga)
diff --git a/content/tech-docs/Tech:Inactivity_policy.md b/content/tech-docs/Tech:Inactivity_policy.md
@@ -45,7 +45,9 @@ If a user resigns due to the fact that they know they will be inactive, they may
 
 If a former sysadmin wishes to come back after having resigned for being inactive, they should follow the [requesting access steps](/tech-docs/techappointment_and_revocation_policy#how-to-request-access) again,. However, instead of the procedure detailed in the [Tech:Appointment and revocation policy](/tech-docs/techappointment_and_revocation_policy), they may be quickly re-added with the common accord of the SRE Management Team.
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Inactivity_policy](https://meta.miraheze.org/wiki/Tech:Inactivity_policy)
diff --git a/content/tech-docs/Tech:Incidents.md b/content/tech-docs/Tech:Incidents.md
@@ -61,7 +61,10 @@ To file a new incident report, fill out the form at [Special:IncidentReports/cre
 
 All reports can be found at [Special:IncidentReports](https://meta.miraheze.org/wiki/Special:IncidentReports). Below are reports made before the new system implementation, and are kept for archival purposes only.
  `{{ {{Special:PrefixIndex/Tech:Incidents/|hideredirects=1}} }}`
-[Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
+
+## Categories
+
+* [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Incidents](https://meta.miraheze.org/wiki/Tech:Incidents)
diff --git a/content/tech-docs/Tech:Internal_ToU_Policy.md b/content/tech-docs/Tech:Internal_ToU_Policy.md
@@ -19,8 +19,10 @@ The Technology team is authorized to enforce the Terms of Use and enact sanction
 * Block or lock any users involved in writing the how-to guides (as they could replicate that information on other wikis); and
 * Alert T&S of the behavior and the action taken by the Technology team.
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
-[Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+* [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Internal_ToU_Policy](https://meta.miraheze.org/wiki/Tech:Internal_ToU_Policy)
diff --git a/content/tech-docs/Tech:Ldap.md b/content/tech-docs/Tech:Ldap.md
@@ -215,7 +215,9 @@ trustandsafety
 
 LDAP can be monitored via Grafana by accessing [this link](https://grafana.wikitide.net/d/uOLD33lMz/ldap?orgId=1).
 
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Ldap](https://meta.miraheze.org/wiki/Tech:Ldap)
diff --git a/content/tech-docs/Tech:Maintenance_policy.md b/content/tech-docs/Tech:Maintenance_policy.md
@@ -64,7 +64,9 @@ title: Tech:Maintenance policy
 
 This policy was initially created by [Universal Omega](https://meta.miraheze.org/wiki/User:Universal_Omega) with contributions from [NotAracham](https://meta.miraheze.org/wiki/User:NotAracham), [Reception123](https://meta.miraheze.org/wiki/User:Reception123), and [Void](https://meta.miraheze.org/wiki/User:Void).
 
-[Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
+## Categories
+
+* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Maintenance_policy](https://meta.miraheze.org/wiki/Tech:Maintenance_policy)
diff --git a/content/tech-docs/Tech:MariaDB.md b/content/tech-docs/Tech:MariaDB.md
@@ -99,8 +99,10 @@ To restore a database from a .idb file following these steps:
 
 * [Restoring mysql tables from ind fpm files and or mysql log bin files](https://dba.stackexchange.com/questions/71596/restoring-mysql-tables-from-ibd-frm-and-mysqllogbin-files)
 
-[Category:Services](https://meta.miraheze.org/wiki/Category:Services)
-[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
+## Categories
+
+* [Category:Services](https://meta.miraheze.org/wiki/Category:Services)
+* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:MariaDB](https://meta.miraheze.org/wiki/Tech:MariaDB)
diff --git a/content/tech-docs/Tech:Matomo.md b/content/tech-docs/Tech:Matomo.md
@@ -12,7 +12,9 @@ To disable 2FA on a specific user account, ssh into matomo151 and run the follow
 
 `./console twofactorauth:disable-2fa-for-user --login=<user>`
 
-[Category:Services](https://meta.miraheze.org/wiki/Category:Services)
+## Categories
+
+* [Category:Services](https://meta.miraheze.org/wiki/Category:Services)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Matomo](https://meta.miraheze.org/wiki/Tech:Matomo)
diff --git a/content/tech-docs/Tech:MediaWiki-Compatibility-de.md b/content/tech-docs/Tech:MediaWiki-Compatibility-de.md
@@ -17,8 +17,10 @@ Unten findest du eine Tabelle von [MediaWiki.org](https://meta.miraheze.org/wiki
 
 * [Browser-Kompatibilität](https://meta.miraheze.org/wiki/mw:Compatibility#Browsers) auf MediaWiki.org.
 
-[Category:Miraheze help](https://meta.miraheze.org/wiki/Category:Miraheze_help)
-[Category:MediaWiki](https://meta.miraheze.org/wiki/Category:MediaWiki)
+## Categories
+
+* [Category:Miraheze help](https://meta.miraheze.org/wiki/Category:Miraheze_help)
+* [Category:MediaWiki](https://meta.miraheze.org/wiki/Category:MediaWiki)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:MediaWiki/Compatibility/de](https://meta.miraheze.org/wiki/Tech:MediaWiki/Compatibility/de)
diff --git a/content/tech-docs/Tech:MediaWiki-Compatibility-en.md b/content/tech-docs/Tech:MediaWiki-Compatibility-en.md
@@ -17,8 +17,10 @@ Below is a table from [MediaWiki.org](https://meta.miraheze.org/wiki/mw:) which
 
 * [Browser compatibility](https://meta.miraheze.org/wiki/mw:Compatibility#Browsers) on MediaWiki.org.
 
-[Category:Miraheze help](https://meta.miraheze.org/wiki/Category:Miraheze_help)
-[Category:MediaWiki](https://meta.miraheze.org/wiki/Category:MediaWiki)
+## Categories
+
+* [Category:Miraheze help](https://meta.miraheze.org/wiki/Category:Miraheze_help)
+* [Category:MediaWiki](https://meta.miraheze.org/wiki/Category:MediaWiki)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:MediaWiki/Compatibility/en](https://meta.miraheze.org/wiki/Tech:MediaWiki/Compatibility/en)
diff --git a/content/tech-docs/Tech:MediaWiki-Compatibility-hi.md b/content/tech-docs/Tech:MediaWiki-Compatibility-hi.md
@@ -17,8 +17,10 @@ Miraheze ब्राउज़रों को तीन श्रेणिय
 
 * MediaWiki.org पर [ब्राउज़र अनुकूलता](https://meta.miraheze.org/wiki/mw:Compatibility#Browsers)।
 
-[Category:Miraheze help](https://meta.miraheze.org/wiki/Category:Miraheze_help)
-[Category:MediaWiki](https://meta.miraheze.org/wiki/Category:MediaWiki)
+## Categories
+
+* [Category:Miraheze help](https://meta.miraheze.org/wiki/Category:Miraheze_help)
+* [Category:MediaWiki](https://meta.miraheze.org/wiki/Category:MediaWiki)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:MediaWiki/Compatibility/hi](https://meta.miraheze.org/wiki/Tech:MediaWiki/Compatibility/hi)