Auto-update Tech namespace pages 2024-09-16 08:46:03.509753

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](/tech-docs/techremoving_an_extension.md)
+* [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)

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](/tech-docs/techinactivity_policy.md)
+See: [Tech:Inactivity policy](/tech-docs/techinactivity_policy)
 
 ## Removal 
 
@@ -26,7 +26,7 @@ The Engineering Manager for the relevant team may propose that a system administ
 
 ### For Inactivity 
 
-See: [Tech:Inactivity policy](/tech-docs/techinactivity_policy.md)
+See: [Tech:Inactivity policy](/tech-docs/techinactivity_policy)
 
 ## Suspension 
 
@@ -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](/tech-docs/techfido2_ssh.md).
+      * If using a FIDO2 key, see [Tech:FIDO2 SSH](/tech-docs/techfido2_ssh).
    * 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).

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](/tech-docs/techvolunteers.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.
+This policy lays out the process by which the [Technology team](/tech-docs/techvolunteers) 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 
 

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](/tech-docs/techproxmox.md).
+**cloud15** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud15](https://meta.miraheze.org/wiki/Tech:Cloud15)

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](/tech-docs/techproxmox.md).
+**cloud16** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud16](https://meta.miraheze.org/wiki/Tech:Cloud16)

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](/tech-docs/techproxmox.md).
+**cloud17** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud17](https://meta.miraheze.org/wiki/Tech:Cloud17)

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](/tech-docs/techproxmox.md).
+**cloud18** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Cloud18](https://meta.miraheze.org/wiki/Tech:Cloud18)

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](/tech-docs/techvarnish.md).
+Miraheze is in the process of migrating to Cloudflare as a replacement of [Varnish](/tech-docs/techvarnish).
 
 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.
 

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](/tech-docs/techgithub.md).
+* **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-docs/techgithub).
 * 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

content/tech-docs/Tech:Compromised_Handling.md

@@ -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](/tech-docs/techsalt.md) (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-docs/techsalt) (Section salt master).
 
 ## Notification of Users 
 

content/tech-docs/Tech:DNS.md

@@ -2,7 +2,7 @@
 title: Tech:DNS
 ---
 
-Miraheze's DNS is self-hosted, on two servers: [ns1](/tech-docs/techns1.md) and [ns2](/tech-docs/techns2.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.
+Miraheze's DNS is self-hosted, on two servers: [ns1](/tech-docs/techns1) and [ns2](/tech-docs/techns2). [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 
 

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](/tech-docs/techmariadb.md).
+**db151** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db151](https://meta.miraheze.org/wiki/Tech:Db151)

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](/tech-docs/techmariadb.md).
+**db161** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db161](https://meta.miraheze.org/wiki/Tech:Db161)

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](/tech-docs/techmariadb.md).
+**db171** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db171](https://meta.miraheze.org/wiki/Tech:Db171)

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](/tech-docs/techmariadb.md).
+**db181** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db181](https://meta.miraheze.org/wiki/Tech:Db181)

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](/tech-docs/techmariadb.md). 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-docs/techmariadb). It currently only hosts non-MediaWiki databases.
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Db182](https://meta.miraheze.org/wiki/Tech:Db182)

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](/tech-docs/techpuppet.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.
+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-docs/techpuppet) 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](/tech-docs/techmw151.md), [mw152](/tech-docs/techmw152.md), [mw161](/tech-docs/techmw161.md), [mw162](/tech-docs/techmw162.md), [mw171](/tech-docs/techmw171.md), [mw172](/tech-docs/techmw172.md), [mw181](/tech-docs/techmw181.md), [mw182](/tech-docs/techmw182.md), [mwtask181](/tech-docs/techmwtask181.md), [test151](/tech-docs/techtest151.md)
+* **Servers**: [mw151](/tech-docs/techmw151), [mw152](/tech-docs/techmw152), [mw161](/tech-docs/techmw161), [mw162](/tech-docs/techmw162), [mw171](/tech-docs/techmw171), [mw172](/tech-docs/techmw172), [mw181](/tech-docs/techmw181), [mw182](/tech-docs/techmw182), [mwtask181](/tech-docs/techmwtask181), [test151](/tech-docs/techtest151)
 
 ### 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](/tech-docs/techmw151.md), [mw152](/tech-docs/techmw152.md), [mw161](/tech-docs/techmw161.md), [mw162](/tech-docs/techmw162.md), [mw171](/tech-docs/techmw171.md), [mw172](/tech-docs/techmw172.md), [mw181](/tech-docs/techmw181.md), [mw182](/tech-docs/techmw182.md), [mwtask181](/tech-docs/techmwtask181.md), [test151](/tech-docs/techtest151.md)
+* **Servers**: [mw151](/tech-docs/techmw151), [mw152](/tech-docs/techmw152), [mw161](/tech-docs/techmw161), [mw162](/tech-docs/techmw162), [mw171](/tech-docs/techmw171), [mw172](/tech-docs/techmw172), [mw181](/tech-docs/techmw181), [mw182](/tech-docs/techmw182), [mwtask181](/tech-docs/techmwtask181), [test151](/tech-docs/techtest151)
 
 ### dns 
 
-[DNS](/tech-docs/techdns.md) (Domain Name System) is the repository that manages all DNS for Miraheze.
+[DNS](/tech-docs/techdns) (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](/tech-docs/techns1.md), [ns2](/tech-docs/techns2.md)
+* **Servers**: [ns1](/tech-docs/techns1), [ns2](/tech-docs/techns2)
 
 ### ssl 
 
-[SSL](/tech-docs/techssl_certificates.md) (Secure Sockets Layer) is the repository that manages all SSL certificates for Miraheze.
+[SSL](/tech-docs/techssl_certificates) (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](/tech-docs/techpuppet181.md)
+* **Servers**: [puppet181](/tech-docs/techpuppet181)
 
 ## 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](/tech-docs/techmwdeploy.md) or manually)</sub>
+* **Servers**: MediaWiki servers<sub>(*reference:* Only if the extension is updated using [mwdeploy](/tech-docs/techmwdeploy) or manually)</sub>
 
 ### ManageWiki 
 

content/tech-docs/Tech:Grafana.md

@@ -6,7 +6,7 @@ Grafana is used to receive metric information from servers in production such as
 
 ## Central Server 
 
-All data is collected on a central server which also serves the [web interface](https://grafana.wikitide.net/). Currently, this server is [mon181](/tech-docs/techmon181.md). All servers have firewall rules opening the relevant ports that are needed, so the central server can communicate with all the clients and clients can send metric information to the central server.
+All data is collected on a central server which also serves the [web interface](https://grafana.wikitide.net/). Currently, this server is [mon181](/tech-docs/techmon181). All servers have firewall rules opening the relevant ports that are needed, so the central server can communicate with all the clients and clients can send metric information to the central server.
 
 ## Adding New Servers 
 

content/tech-docs/Tech:Graylog.md

@@ -2,11 +2,11 @@
 title: Tech:Graylog
 ---
 
-**Graylog** is a [log management solution](https://www.graylog.org/) for logs stored on the servers. The web interface is available at [https://logging.wikitide.net/](https://logging.wikitide.net/). Access is restricted to [Technology team department personnel](/tech-docs/techvolunteers.md). Said people can use their LDAP credentials for authentication.
+**Graylog** is a [log management solution](https://www.graylog.org/) for logs stored on the servers. The web interface is available at [https://logging.wikitide.net/](https://logging.wikitide.net/). Access is restricted to [Technology team department personnel](/tech-docs/techvolunteers). Said people can use their LDAP credentials for authentication.
 
 ## Architecture 
 
-Graylog runs on [graylog161.wikitide.net](/tech-docs/techgraylog161.md) as of now. There are three daemons running there: `graylog-server` for the actual log management, `opensearch` for storing the logs and `mongod` for storing Graylog's configuration.
+Graylog runs on [graylog161.wikitide.net](/tech-docs/techgraylog161) as of now. There are three daemons running there: `graylog-server` for the actual log management, `opensearch` for storing the logs and `mongod` for storing Graylog's configuration.
 
 ```
                                                                                                                   
@@ -53,7 +53,7 @@ Graylog has a [search syntax](https://docs.graylog.org/en/4.0/pages/searching/qu
 
 ## Access 
 
-For security reasons, the Graylog interface is inaccessible without a [SOCKS5 proxy](https://meta.miraheze.org/wiki/w:SOCKS#SOCKS5), just like [Proxmox' interface](/tech-docs/techproxmox.md). To make the process of using tunnels as easy as possible, please install SmartProxy: [Chrome](https://chrome.google.com/webstore/detail/smartproxy/jogcnplbkgkfdakgdenhlpcfhjioidoj?hl=nl) or [Firefox](https://addons.mozilla.org/en-US/firefox/addon/smartproxy/). We'll be using port 8089 (although other ports will work too) on your desktop or laptop, which will be used for a SOCKS5 proxy over SSH. If you have access to graylog161, you can use graylog161.wikitide.net. If you don't have access to graylog161, use either of the Bastion servers (bast*.wikitide.net).
+For security reasons, the Graylog interface is inaccessible without a [SOCKS5 proxy](https://meta.miraheze.org/wiki/w:SOCKS#SOCKS5), just like [Proxmox' interface](/tech-docs/techproxmox). To make the process of using tunnels as easy as possible, please install SmartProxy: [Chrome](https://chrome.google.com/webstore/detail/smartproxy/jogcnplbkgkfdakgdenhlpcfhjioidoj?hl=nl) or [Firefox](https://addons.mozilla.org/en-US/firefox/addon/smartproxy/). We'll be using port 8089 (although other ports will work too) on your desktop or laptop, which will be used for a SOCKS5 proxy over SSH. If you have access to graylog161, you can use graylog161.wikitide.net. If you don't have access to graylog161, use either of the Bastion servers (bast*.wikitide.net).
 
 In SmartProxy, create a proxy server: Proxy Server > Add server > Name = "WikiTide Proxy", Address = "127.0.0.1", Port = "8089", Protocol = "SOCKS5" > Save. Afterwards, create a proxy rule: Proxy Rules > Add rule > Rule type = "Search Domain and SubDomain", Domain = "logging.wikitide.net", then "Apply Proxy" to "WikiTide Proxy" > Save and then click "Save" on the bottom of the page as well.