Auto-update Tech namespace pages 2024-09-16 08:32:33.382468

miraheze · Sep 16, 2024 · fb5910c · fb5910c
1 parent e2a701c
commit fb5910c
Show file tree

Hide file tree

Showing 99 changed files with 193 additions and 193 deletions.
diff --git a/content/tech-docs/Tech:Adding_a_new_extension.md b/content/tech-docs/Tech:Adding_a_new_extension.md
@@ -21,7 +21,7 @@ It should be noted that it is a good idea to add any configuration variable the
 ## See also 
 
 * [Updating an extension](https://meta.miraheze.org/wiki/Tech:Updating_an_extension)
-* [Removing an extension](https://meta.miraheze.org/wiki/Tech:Removing_an_extension)
+* [Removing an extension](Tech:Removing_an_extension.md)
 
 [Category:Guides](https://meta.miraheze.org/wiki/Category:Guides)
 [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)

diff --git a/content/tech-docs/Tech:Appointment_and_revocation_policy.md b/content/tech-docs/Tech:Appointment_and_revocation_policy.md
@@ -14,7 +14,7 @@ While not necessary, it is encouraged that all SRE take part in the discussion a
 
 ## Re-appointment after inactivity 
 
-See: [Tech:Inactivity policy](https://meta.miraheze.org/wiki/Tech:Inactivity_policy)
+See: [Tech:Inactivity policy](Tech:Inactivity_policy.md)
 
 ## Removal 
 
@@ -26,7 +26,7 @@ The Engineering Manager for the relevant team may propose that a system administ
 
 ### For Inactivity 
 
-See: [Tech:Inactivity policy](https://meta.miraheze.org/wiki/Tech:Inactivity_policy)
+See: [Tech:Inactivity policy](Tech:Inactivity_policy.md)
 
 ## Suspension 
 
@@ -38,7 +38,7 @@ In ultimate emergencies, such as compromised accounts, any member with the relev
 
 ### New Access 
 
-This applies to people, who do not have shell access yet. After you have articulated a valid reason for requesting shell access, and followed the instructions below, your request will be dealt with as [described above](#appointment).
+This applies to people, who do not have shell access yet. After you have articulated a valid reason for requesting shell access, and followed the instructions below, your request will be dealt with as [described above](#Appointment).
 * Ensure you have an account on [GitHub](https://meta.miraheze.org/wiki/github:) and [Phorge](https://meta.miraheze.org/wiki/phorge:) (which requires a Miraheze account).
 * Login into Phorge, and [fill in this form](https://meta.miraheze.org/wiki/phorge:maniphest/task/edit/form/17/) (do not forget to replace "[USERNAME]" with your username!). The form should contain the following information:
    * Miraheze Username
@@ -47,7 +47,7 @@ This applies to people, who do not have shell access yet. After you have articul
    * A freshly generated 4096 bit RSA or ed25519 keypair, protected with a secure password.
       * Obviously you should only give us the public key, keep the private key private.
       * This key should not be used for non-Miraheze servers!
-      * If using a FIDO2 key, see [Tech:FIDO2 SSH](https://meta.miraheze.org/wiki/Tech:FIDO2_SSH).
+      * If using a FIDO2 key, see [Tech:FIDO2 SSH](Tech:FIDO2_SSH.md).
    * Description of the access you need. If you require sudo rights, please do not forget to include that as well.
    * The reason you need shell access.
    * A verification that your Miraheze, GitHub and Phorge accounts are owned by you. This can be accomplished by a) pasting the public key of your keypair on your **Miraheze Meta** user page (or another page in your user namespace) and b) creating a GitHub repository with a file containing the public key (or committing your public key to an already existing repository).

diff --git a/content/tech-docs/Tech:CSP_Policy.md b/content/tech-docs/Tech:CSP_Policy.md
@@ -4,7 +4,7 @@ title: Tech:CSP Policy
 
 `{{ {{Tech policy}} }}`
 
-This policy lays out the process by which the [Technology team](https://meta.miraheze.org/wiki/Tech:Volunteers) may approve new additions to the Content Security Policy (CSP). Sites added to the CSP may have content on that domain loaded by all Miraheze wikis. CSP approvals are generally the responsibility of MediaWiki Specialists, as a function of MediaWiki security. Though, any step in the approvals process may be handled by an Infrastructure Specialist.
+This policy lays out the process by which the [Technology team](Tech:Volunteers.md) may approve new additions to the Content Security Policy (CSP). Sites added to the CSP may have content on that domain loaded by all Miraheze wikis. CSP approvals are generally the responsibility of MediaWiki Specialists, as a function of MediaWiki security. Though, any step in the approvals process may be handled by an Infrastructure Specialist.
 
 ## Questions 
 

diff --git a/content/tech-docs/Tech:Cloud15.md b/content/tech-docs/Tech:Cloud15.md
@@ -19,7 +19,7 @@ title: Tech:Cloud15
 }} }}
 ```
 
-**cloud15** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](https://meta.miraheze.org/wiki/Tech:Proxmox).
+**cloud15** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](Tech:Proxmox.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud15](https://meta.miraheze.org/wiki/Tech:Cloud15)
diff --git a/content/tech-docs/Tech:Cloud16.md b/content/tech-docs/Tech:Cloud16.md
@@ -19,7 +19,7 @@ title: Tech:Cloud16
 }} }}
 ```
 
-**cloud16** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](https://meta.miraheze.org/wiki/Tech:Proxmox).
+**cloud16** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](Tech:Proxmox.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud16](https://meta.miraheze.org/wiki/Tech:Cloud16)
diff --git a/content/tech-docs/Tech:Cloud17.md b/content/tech-docs/Tech:Cloud17.md
@@ -19,7 +19,7 @@ title: Tech:Cloud17
 }} }}
 ```
 
-**cloud17** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](https://meta.miraheze.org/wiki/Tech:Proxmox).
+**cloud17** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](Tech:Proxmox.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud17](https://meta.miraheze.org/wiki/Tech:Cloud17)
diff --git a/content/tech-docs/Tech:Cloud18.md b/content/tech-docs/Tech:Cloud18.md
@@ -19,7 +19,7 @@ title: Tech:Cloud18
 }} }}
 ```
 
-**cloud18** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](https://meta.miraheze.org/wiki/Tech:Proxmox).
+**cloud18** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](Tech:Proxmox.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud18](https://meta.miraheze.org/wiki/Tech:Cloud18)
diff --git a/content/tech-docs/Tech:Cloudflare.md b/content/tech-docs/Tech:Cloudflare.md
@@ -2,7 +2,7 @@
 title: Tech:Cloudflare
 ---
 
-Miraheze is in the process of migrating to Cloudflare as a replacement of [Varnish](https://meta.miraheze.org/wiki/Tech:Varnish).
+Miraheze is in the process of migrating to Cloudflare as a replacement of [Varnish](Tech:Varnish.md).
 
 Currently, wikis on all Miraheze-owned domains (except for *.wikitide.net/*.wikitide.org) and custom domain wikis not using Miraheze's DNS servers (but rather [CNAME](https://meta.miraheze.org/wiki/w:CNAME)s or [ANAME](https://meta.miraheze.org/wiki/w:ANAME)s) use Cloudflare.
 

diff --git a/content/tech-docs/Tech:Communication.md b/content/tech-docs/Tech:Communication.md
@@ -12,7 +12,7 @@ This page aims to document our communication channels, and outline a general str
 * **[Hund](https://meta.miraheze.org/wiki/Tech:Hund)**. Your standard status page. Available at [status.miraheze.wiki](https://status.miraheze.wiki), and additionally has multiple types of subscriptions.
 * **[Tech:SRE noticeboard](https://meta.miraheze.org/wiki/Tech:SRE_noticeboard)**. A page hosting on-wiki announcements by SRE.
 * **Twitter, Mastodon and Facebook**. Social media.
-* **On-wiki sitenotices**. Sitenotices that are shown on either wikis meeting a specific condition ("targeted"), such as having an extension enabled, or shown everywhere ("global"). Managed at [mw-config/Sitenotice.php](https://github.com/miraheze/mw-config/blob/master/Sitenotice.php) on [GitHub](https://meta.miraheze.org/wiki/Tech:GitHub).
+* **On-wiki sitenotices**. Sitenotices that are shown on either wikis meeting a specific condition ("targeted"), such as having an extension enabled, or shown everywhere ("global"). Managed at [mw-config/Sitenotice.php](https://github.com/miraheze/mw-config/blob/master/Sitenotice.php) on [GitHub](Tech:GitHub.md).
 * Less importantly, **[Phorge](https://meta.miraheze.org/wiki/Phorge)**. While it can be argued comments and tasks there are not for the community at-large, some may use these for the latest "announcements", especially in tasks related to farm-wide issues. Just something to keep in mind.
 
 ## Strategy

diff --git a/content/tech-docs/Tech:Compromised_Handling.md b/content/tech-docs/Tech:Compromised_Handling.md
@@ -66,7 +66,7 @@ MariaDB databases include wiki databases and other misc. services. If a database
 
 ### MariaDB - passwords 
 
-The level of severity depends on which password is assumed to have been compromised. An evaluation of all databases that may have been compromised should be done after immediately resetting the password that was compromised and all below (if root). The process [for databases above](#mariadb---databases) applies mostly as a compromised password compromises databases.
+The level of severity depends on which password is assumed to have been compromised. An evaluation of all databases that may have been compromised should be done after immediately resetting the password that was compromised and all below (if root). The process [for databases above](#MariaDB - database(s)) applies mostly as a compromised password compromises databases.
 
 The key should be updated both in puppet and manually on the server (Puppet does not automatically change SQL passwords).
 
@@ -84,7 +84,7 @@ All traffic should be viewed as compromised (as traffic may be decrypted though
 
 ### Salt (Private Keys) 
 
-All servers should be viewed as compromised. All private keys should be regenerated. You should remove all hosts immediately (by following [Salt](https://meta.miraheze.org/wiki/Tech:Salt) (Section salt master).
+All servers should be viewed as compromised. All private keys should be regenerated. You should remove all hosts immediately (by following [Salt](Tech:Salt.md) (Section salt master).
 
 ## Notification of Users 
 

diff --git a/content/tech-docs/Tech:DNS.md b/content/tech-docs/Tech:DNS.md
@@ -2,7 +2,7 @@
 title: Tech:DNS
 ---
 
-Miraheze's DNS is self-hosted, on two servers: [ns1](https://meta.miraheze.org/wiki/Tech:Ns1) and [ns2](https://meta.miraheze.org/wiki/Tech:Ns2). [GDNSD](//github.com/gdnsd/gdnsd) is the software used for this task, and we chose it because GDNSD is open-source, fast, and easy.
+Miraheze's DNS is self-hosted, on two servers: [ns1](Tech:Ns1.md) and [ns2](Tech:Ns2.md). [GDNSD](//github.com/gdnsd/gdnsd) is the software used for this task, and we chose it because GDNSD is open-source, fast, and easy.
 
 ## Configuration 
 

diff --git a/content/tech-docs/Tech:Db151.md b/content/tech-docs/Tech:Db151.md
@@ -20,7 +20,7 @@ title: Tech:Db151
 }} }}
 ```
 
-**db151** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](https://meta.miraheze.org/wiki/Tech:MariaDB).
+**db151** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](Tech:MariaDB.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db151](https://meta.miraheze.org/wiki/Tech:Db151)
diff --git a/content/tech-docs/Tech:Db161.md b/content/tech-docs/Tech:Db161.md
@@ -20,7 +20,7 @@ title: Tech:Db161
 }} }}
 ```
 
-**db161** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](https://meta.miraheze.org/wiki/Tech:MariaDB).
+**db161** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](Tech:MariaDB.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db161](https://meta.miraheze.org/wiki/Tech:Db161)
diff --git a/content/tech-docs/Tech:Db171.md b/content/tech-docs/Tech:Db171.md
@@ -20,7 +20,7 @@ title: Tech:Db171
 }} }}
 ```
 
-**db171** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](https://meta.miraheze.org/wiki/Tech:MariaDB).
+**db171** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](Tech:MariaDB.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db171](https://meta.miraheze.org/wiki/Tech:Db171)
diff --git a/content/tech-docs/Tech:Db181.md b/content/tech-docs/Tech:Db181.md
@@ -20,7 +20,7 @@ title: Tech:Db181
 }} }}
 ```
 
-**db181** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](https://meta.miraheze.org/wiki/Tech:MariaDB).
+**db181** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](Tech:MariaDB.md).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db181](https://meta.miraheze.org/wiki/Tech:Db181)
diff --git a/content/tech-docs/Tech:Db182.md b/content/tech-docs/Tech:Db182.md
@@ -20,7 +20,7 @@ title: Tech:Db182
 }} }}
 ```
 
-**db182** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](https://meta.miraheze.org/wiki/Tech:MariaDB). It currently only hosts non-MediaWiki databases.
+**db182** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](Tech:MariaDB.md). It currently only hosts non-MediaWiki databases.
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db182](https://meta.miraheze.org/wiki/Tech:Db182)
diff --git a/content/tech-docs/Tech:GHSA.md b/content/tech-docs/Tech:GHSA.md
@@ -11,7 +11,7 @@ Advisories should only be created for software we build for external parties - t
 If you need to create an advisory, follow the steps below:
 * Go to the repository that is relevant for the code you wish to create an advisory for.
 * Select the 'Security' tab and then on the side menu, select 'Security Advisories' and then press the green button 'New Draft Security Advisory'.
-* Fill out the information to the best of your knowledge currently. If unsure, leave it blank or insert 'N/K'. See an explanation of the [CVSS](#making-an-assessment-using-cvss) matrix.
+* Fill out the information to the best of your knowledge currently. If unsure, leave it blank or insert 'N/K'. See an explanation of the [CVSS](#Making an Assessment Using CVSS) matrix.
 * Once created, on the right-hand side there is an option to invite 'Collaborators' to see the advisory. This can include anyone who may require access to the advisory prior to publishing, such as 'Security' project members who are not in Site Reliability Engineering, the reporter, or any trusted volunteer developer who has or is working on a patch.
 
 **If a fix is possible:**

diff --git a/content/tech-docs/Tech:GitHub.md b/content/tech-docs/Tech:GitHub.md
@@ -4,7 +4,7 @@ title: Tech:GitHub
 
 [GitHub](https://meta.miraheze.org/wiki/github:) is the service we use to host our open-source repositories. They can be found [here](https://meta.miraheze.org/wiki/github:miraheze).
 
-Push access to the repositories is limited to [system administrators](https://meta.miraheze.org/wiki/Tech:SRE_Volunteers), but any user can make a pull request. [Puppet](https://meta.miraheze.org/wiki/Tech:Puppet) runs every 30 minutes (except MediaWiki extensions or skins) and can be run manually on each server by a [system administrator](https://meta.miraheze.org/wiki/Tech:SRE_Volunteers). It is recommended to read the "README.md" file for a repository before contributing to it.
+Push access to the repositories is limited to [system administrators](https://meta.miraheze.org/wiki/Tech:SRE_Volunteers), but any user can make a pull request. [Puppet](Tech:Puppet.md) runs every 30 minutes (except MediaWiki extensions or skins) and can be run manually on each server by a [system administrator](https://meta.miraheze.org/wiki/Tech:SRE_Volunteers). It is recommended to read the "README.md" file for a repository before contributing to it.
 
 ## Production repositories 
 
@@ -18,33 +18,33 @@ Puppet is the repository that manages all services/servers.
 
 mw-config (MediaWiki configuration) is the repository that manages settings for MediaWiki.
 * **Push Access**: [Site Reliability Engineers (Infrastructure)](https://meta.miraheze.org/wiki/Tech:Organisation#Team:_Infrastructure,_Site_Reliability_Engineering), [MediaWiki Engineers](https://meta.miraheze.org/wiki/Tech:Organisation#Team:_MediaWiki,_Site_Reliability_Engineering)
-* **Servers**: [mw151](https://meta.miraheze.org/wiki/Tech:Mw151), [mw152](https://meta.miraheze.org/wiki/Tech:Mw152), [mw161](https://meta.miraheze.org/wiki/Tech:Mw161), [mw162](https://meta.miraheze.org/wiki/Tech:Mw162), [mw171](https://meta.miraheze.org/wiki/Tech:Mw171), [mw172](https://meta.miraheze.org/wiki/Tech:Mw172), [mw181](https://meta.miraheze.org/wiki/Tech:Mw181), [mw182](https://meta.miraheze.org/wiki/Tech:Mw182), [mwtask181](https://meta.miraheze.org/wiki/Tech:Mwtask181), [test151](https://meta.miraheze.org/wiki/Tech:Test151)
+* **Servers**: [mw151](Tech:Mw151.md), [mw152](Tech:Mw152.md), [mw161](Tech:Mw161.md), [mw162](Tech:Mw162.md), [mw171](Tech:Mw171.md), [mw172](Tech:Mw172.md), [mw181](Tech:Mw181.md), [mw182](Tech:Mw182.md), [mwtask181](Tech:Mwtask181.md), [test151](Tech:Test151.md)
 
 ### mediawiki 
 
 mediawiki is the repository that manages the MediaWiki source code, skins, and extensions.
 * **Push Access**: [Site Reliability Engineers (Infrastructure)](https://meta.miraheze.org/wiki/Tech:Organisation#Team:_Infrastructure,_Site_Reliability_Engineering), [MediaWiki Engineers](https://meta.miraheze.org/wiki/Tech:Organisation#Team:_MediaWiki,_Site_Reliability_Engineering)
-* **Servers**: [mw151](https://meta.miraheze.org/wiki/Tech:Mw151), [mw152](https://meta.miraheze.org/wiki/Tech:Mw152), [mw161](https://meta.miraheze.org/wiki/Tech:Mw161), [mw162](https://meta.miraheze.org/wiki/Tech:Mw162), [mw171](https://meta.miraheze.org/wiki/Tech:Mw171), [mw172](https://meta.miraheze.org/wiki/Tech:Mw172), [mw181](https://meta.miraheze.org/wiki/Tech:Mw181), [mw182](https://meta.miraheze.org/wiki/Tech:Mw182), [mwtask181](https://meta.miraheze.org/wiki/Tech:Mwtask181), [test151](https://meta.miraheze.org/wiki/Tech:Test151)
+* **Servers**: [mw151](Tech:Mw151.md), [mw152](Tech:Mw152.md), [mw161](Tech:Mw161.md), [mw162](Tech:Mw162.md), [mw171](Tech:Mw171.md), [mw172](Tech:Mw172.md), [mw181](Tech:Mw181.md), [mw182](Tech:Mw182.md), [mwtask181](Tech:Mwtask181.md), [test151](Tech:Test151.md)
 
 ### dns 
 
-[DNS](https://meta.miraheze.org/wiki/Tech:DNS) (Domain Name System) is the repository that manages all DNS for Miraheze.
+[DNS](Tech:DNS.md) (Domain Name System) is the repository that manages all DNS for Miraheze.
 * **Push Access**: [Site Reliability Engineers (Infrastructure)](https://meta.miraheze.org/wiki/Tech:Organisation#Team:_Infrastructure,_Site_Reliability_Engineering)
-* **Servers**: [ns1](https://meta.miraheze.org/wiki/Tech:Ns1), [ns2](https://meta.miraheze.org/wiki/Tech:Ns2)
+* **Servers**: [ns1](Tech:Ns1.md), [ns2](Tech:Ns2.md)
 
 ### ssl 
 
-[SSL](https://meta.miraheze.org/wiki/Tech:SSL_certificates) (Secure Sockets Layer) is the repository that manages all SSL certificates for Miraheze.
+[SSL](Tech:SSL_certificates.md) (Secure Sockets Layer) is the repository that manages all SSL certificates for Miraheze.
 * **Push Access**: [Site Reliability Engineers (Infrastructure)](https://meta.miraheze.org/wiki/Tech:Organisation#Team:_Infrastructure,_Site_Reliability_Engineering), ssl-admins
-* **Servers**: [puppet181](https://meta.miraheze.org/wiki/Tech:Puppet181)
+* **Servers**: [puppet181](Tech:Puppet181.md)
 
 ## MediaWiki extensions and skins 
 
 ### CreateWiki 
 
 [CreateWiki](https://github.com/miraheze/CreateWiki) is a MediaWiki extension to request and create wikis on Miraheze.
 * **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n<sub>(*reference:* Currently [@translatewiki](https://github.com/translatewiki) only)</sub>
-* **Servers**: MediaWiki servers<sub>(*reference:* Only if the extension is updated using [mwdeploy](https://meta.miraheze.org/wiki/Tech:Mwdeploy) or manually)</sub>
+* **Servers**: MediaWiki servers<sub>(*reference:* Only if the extension is updated using [mwdeploy](Tech:Mwdeploy.md) or manually)</sub>
 
 ### ManageWiki