Auto-update Tech namespace pages 2024-09-16 07:23:50.595146

miraheze · Sep 16, 2024 · cda105e · cda105e
1 parent 8f953f4
commit cda105e
Show file tree

Hide file tree

Showing 193 changed files with 482 additions and 482 deletions.
diff --git a/content/tech-docs/.Tech:Adding_a_new_extension.md.swp b/content/tech-docs/.Tech:Adding_a_new_extension.md.swp
diff --git a/content/tech-docs/.Tech:Appointment_and_revocation_policy.md.swp b/content/tech-docs/.Tech:Appointment_and_revocation_policy.md.swp
diff --git a/content/tech-docs/Tech:2018_Infrastructure_Assessment.md b/content/tech-docs/Tech:2018_Infrastructure_Assessment.md
@@ -27,4 +27,4 @@ This is a page designed to be a working ground for analysing the infrastructure
 | [test1](https://meta.miraheze.org/wiki/Tech:test1) | Testing | mediawiki, salt-minion | CPU: 1x2.40GHz | 40G | 1GB | $3.50 |
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:2018_Infrastructure_Assessment
+**Source**: [https://meta.miraheze.org/wiki/Tech:2018_Infrastructure_Assessment](https://meta.miraheze.org/wiki/Tech:2018_Infrastructure_Assessment)
diff --git a/content/tech-docs/Tech:Adding_a_new_extension.md b/content/tech-docs/Tech:Adding_a_new_extension.md
@@ -27,4 +27,4 @@ It should be noted that it is a good idea to add any configuration variable the
 [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
+**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
@@ -62,4 +62,4 @@ If you already have a shell account and want to get extra privileges (or are req
 [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Appointment_and_revocation_policy
+**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:Bast161.md b/content/tech-docs/Tech:Bast161.md
@@ -23,4 +23,4 @@ title: Tech:Bast161
 **bast161** is a FiberState server in Salt Lake City, Utah running Debian Bookworm.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Bast161
+**Source**: [https://meta.miraheze.org/wiki/Tech:Bast161](https://meta.miraheze.org/wiki/Tech:Bast161)
diff --git a/content/tech-docs/Tech:Bast181.md b/content/tech-docs/Tech:Bast181.md
@@ -23,4 +23,4 @@ title: Tech:Bast181
 **bast181** is a FiberState server in Salt Lake City, Utah running Debian Bookworm.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Bast181
+**Source**: [https://meta.miraheze.org/wiki/Tech:Bast181](https://meta.miraheze.org/wiki/Tech:Bast181)
diff --git a/content/tech-docs/Tech:CSP_Policy.md b/content/tech-docs/Tech:CSP_Policy.md
@@ -33,4 +33,4 @@ In the event of a dispute or situation not covered by this policy, the Director
 [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:CSP_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:Cloud15.md b/content/tech-docs/Tech:Cloud15.md
@@ -22,4 +22,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Cloud15
+**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
@@ -22,4 +22,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Cloud16
+**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
@@ -22,4 +22,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Cloud17
+**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
@@ -22,4 +22,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Cloud18
+**Source**: [https://meta.miraheze.org/wiki/Tech:Cloud18](https://meta.miraheze.org/wiki/Tech:Cloud18)
diff --git a/content/tech-docs/Tech:Cloud_Server_Comparison.md b/content/tech-docs/Tech:Cloud_Server_Comparison.md
@@ -32,4 +32,4 @@ This is as a good as direct comparsion but is expected to show the reasonable eq
 | [lizardfs6](https://meta.miraheze.org/wiki/Tech:lizardfs6) | gluster1 | cloud2 | Paladox | `{{ {{done}} }}` |
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Cloud_Server_Comparison
+**Source**: [https://meta.miraheze.org/wiki/Tech:Cloud_Server_Comparison](https://meta.miraheze.org/wiki/Tech:Cloud_Server_Comparison)
diff --git a/content/tech-docs/Tech:Cloudflare.md b/content/tech-docs/Tech:Cloudflare.md
@@ -22,4 +22,4 @@ Keep in mind that this check is done over HTTPS and that Cloudflare is verifying
 * Click save at the bottom of the page and you're done.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Cloudflare
+**Source**: [https://meta.miraheze.org/wiki/Tech:Cloudflare](https://meta.miraheze.org/wiki/Tech:Cloudflare)
diff --git a/content/tech-docs/Tech:Communication.md b/content/tech-docs/Tech:Communication.md
@@ -34,4 +34,4 @@ Not all channels are made the same. Some, like on-wiki sitenotices, are very int
 For example, while sitenotices are intrusive, you ensure that everyone on a Miraheze wiki at that time knows what's going on. Therefore, these are better reserved for farm-wide issues in the case of global sitenotices, or for extensions disabled due to security issues, in the case of targeted sitenotices.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Communication
+**Source**: [https://meta.miraheze.org/wiki/Tech:Communication](https://meta.miraheze.org/wiki/Tech:Communication)
diff --git a/content/tech-docs/Tech:Compromised_Handling.md b/content/tech-docs/Tech:Compromised_Handling.md
@@ -96,4 +96,4 @@ Under EU law, we're required to notify all European users in the event of a brea
 [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Compromised_Handling
+**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
@@ -36,4 +36,4 @@ Failure to adhere to this conduct policy may result in disciplinary action, up t
 [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Conduct_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
@@ -14,7 +14,7 @@ Our GDNSD configuration can be found at [GitHub](//github.com/miraheze/dns), and
 
 ### zones 
 
-DNS records (for one domain name) are stored in a zone (e.g. https://raw.githubusercontent.com/miraheze/dns/master/zones/wikitide.net).
+DNS records (for one domain name) are stored in a zone (e.g. [https://raw.githubusercontent.com/miraheze/dns/master/zones/wikitide.net](https://raw.githubusercontent.com/miraheze/dns/master/zones/wikitide.net)).
 
 ## Deployment 
 
@@ -25,4 +25,4 @@ The system should be moved to manual at some point, though there is not enough r
 [Category:Services](https://meta.miraheze.org/wiki/Category:Services)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:DNS
+**Source**: [https://meta.miraheze.org/wiki/Tech:DNS](https://meta.miraheze.org/wiki/Tech:DNS)
diff --git a/content/tech-docs/Tech:Data_Processing_Inventory.md b/content/tech-docs/Tech:Data_Processing_Inventory.md
@@ -10,9 +10,9 @@ At the [Board meeting of October 23, 2020](https://meta.miraheze.org/wiki/Board/
 
 | Processor | Website | Jurisdiction | Data processing agreement | Purpose | Data |
 | --- | --- | --- | --- | --- | --- |
-| DigitalOcean, LLC | https://www.digitalocean.com/ | United States | https://www.digitalocean.com/legal/data-processing-agreement/ | Hosting infrastructure | Usernames, real names, email addresses, IP addresses, (private) wiki content, passwords, optional user information, other usage information |
-| OVH | https://www.ovh.co.uk/ | France | https://www.ovh.co.uk/support/termsofservice/Data%20Processing%20Agreement_UK.pdf | Hosting infrastructure | Usernames, real names, email addresses, IP addresses, (private) wiki content, passwords, optional user information, other usage information |
-| RamNode LLC | https://ramnode.com/ | United States | https://www.ramnode.com/gdpr-dpa.pdf | Hosting infrastructure | Usernames, real names, email addresses, IP addresses, (private) wiki content, passwords, optional user information, other usage information |
+| DigitalOcean, LLC | [https://www.digitalocean.com/](https://www.digitalocean.com/) | United States | [https://www.digitalocean.com/legal/data-processing-agreement/](https://www.digitalocean.com/legal/data-processing-agreement/) | Hosting infrastructure | Usernames, real names, email addresses, IP addresses, (private) wiki content, passwords, optional user information, other usage information |
+| OVH | [https://www.ovh.co.uk/](https://www.ovh.co.uk/) | France | [https://www.ovh.co.uk/support/termsofservice/Data%20Processing%20Agreement_UK.pdf](https://www.ovh.co.uk/support/termsofservice/Data%20Processing%20Agreement_UK.pdf) | Hosting infrastructure | Usernames, real names, email addresses, IP addresses, (private) wiki content, passwords, optional user information, other usage information |
+| RamNode LLC | [https://ramnode.com/](https://ramnode.com/) | United States | [https://www.ramnode.com/gdpr-dpa.pdf](https://www.ramnode.com/gdpr-dpa.pdf) | Hosting infrastructure | Usernames, real names, email addresses, IP addresses, (private) wiki content, passwords, optional user information, other usage information |
 
 ## Data processing 
 
@@ -39,4 +39,4 @@ At the [Board meeting of October 23, 2020](https://meta.miraheze.org/wiki/Board/
 
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Data_Processing_Inventory
+**Source**: [https://meta.miraheze.org/wiki/Tech:Data_Processing_Inventory](https://meta.miraheze.org/wiki/Tech:Data_Processing_Inventory)
diff --git a/content/tech-docs/Tech:Db151.md b/content/tech-docs/Tech:Db151.md
@@ -23,4 +23,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Db151
+**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
@@ -23,4 +23,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Db161
+**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
@@ -23,4 +23,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Db171
+**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
@@ -23,4 +23,4 @@ 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).
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Db181
+**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
@@ -23,4 +23,4 @@ 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.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Db182
+**Source**: [https://meta.miraheze.org/wiki/Tech:Db182](https://meta.miraheze.org/wiki/Tech:Db182)
diff --git a/content/tech-docs/Tech:Delete_a_wiki.md b/content/tech-docs/Tech:Delete_a_wiki.md
@@ -20,4 +20,4 @@ Performing the deletion if 14 days have **not** passed:
 [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
+**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
@@ -12,4 +12,4 @@ While quite a rare occurrence, it sometimes happens that a user is left with glo
 [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
+**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
@@ -15,4 +15,4 @@ To delete or move large batches of pages on a wiki, execute the following comman
 [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
+**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:Deployment_Policy.md b/content/tech-docs/Tech:Deployment_Policy.md
@@ -37,4 +37,4 @@ The final say with any deployment rests with the deployer. It is perfectly accep
 Press space to (un)select and enter to run.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Deployment_Policy
+**Source**: [https://meta.miraheze.org/wiki/Tech:Deployment_Policy](https://meta.miraheze.org/wiki/Tech:Deployment_Policy)
diff --git a/content/tech-docs/Tech:Experimental_Wikis.md b/content/tech-docs/Tech:Experimental_Wikis.md
@@ -17,4 +17,4 @@ The following features are enabled on experimental wikis:
 * [JQuery Migrate](https://github.com/jquery/jquery-migrate) (now disabled)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Experimental_Wikis
+**Source**: [https://meta.miraheze.org/wiki/Tech:Experimental_Wikis](https://meta.miraheze.org/wiki/Tech:Experimental_Wikis)
diff --git a/content/tech-docs/Tech:FIDO2_SSH.md b/content/tech-docs/Tech:FIDO2_SSH.md
@@ -16,13 +16,13 @@ Generate your key via `ssh-keygen -t ed25519-sk -C "comment"`. This will create
 * no-touch-required keys are not allowed.
 * For added security, do not use resident/discoverable keys.
 
-This will create your standard public key, and a key handle/identification. This identification is not the private key itself. It is only useful to the specific hardware key you used to create the SSH key, so don't lose it and **don't let anyone other than you use it!** However, **treat the identification as if it was the private key anyway**, so make sure to choose a good passphrase (what it is exactly depends on how your key handles these types of keys, see https://www.yubico.com/blog/yubicos-u2f-key-wrapping/ for how this works on Yubikeys).
+This will create your standard public key, and a key handle/identification. This identification is not the private key itself. It is only useful to the specific hardware key you used to create the SSH key, so don't lose it and **don't let anyone other than you use it!** However, **treat the identification as if it was the private key anyway**, so make sure to choose a good passphrase (what it is exactly depends on how your key handles these types of keys, see [https://www.yubico.com/blog/yubicos-u2f-key-wrapping/](https://www.yubico.com/blog/yubicos-u2f-key-wrapping/) for how this works on Yubikeys).
 
 ## Getting the key on Miraheze
 
 Fork [miraheze/puppet](https://github.com/miraheze/puppet) on GitHub, go to `modules/users/data/data.yaml` and look for your shell account. Replace your SSH public key with your newly generated public key. Get a hold of someone from Infrastructure if you yourself do not have write access to Puppet.
 
-If you use signed commits or OpenPGP, now would be a good time to use them for extra assurance. Example: https://github.com/miraheze/puppet/pull/3203.
+If you use signed commits or OpenPGP, now would be a good time to use them for extra assurance. Example: [https://github.com/miraheze/puppet/pull/3203](https://github.com/miraheze/puppet/pull/3203).
 
 ## Account recovery
 
@@ -39,4 +39,4 @@ Ignore this warning at your own peril: If your key stops working, it could becom
 * [Pisces's guide to get it working on Windows](https://meta.miraheze.org/wiki/User:Pisces/FIDO2_SSH_on_Windows)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:FIDO2_SSH
+**Source**: [https://meta.miraheze.org/wiki/Tech:FIDO2_SSH](https://meta.miraheze.org/wiki/Tech:FIDO2_SSH)
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
@@ -36,4 +36,4 @@ After running that make sure you exit shell.php or sql.php (if using) and rerun
 [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
+**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-Written_Security_Disclosure_Template.md b/content/tech-docs/Tech:GHSA-Written_Security_Disclosure_Template.md
@@ -33,4 +33,4 @@ title: Tech:GHSA/Written Security Disclosure Template
 Any further questions that a user wishes to keep private can be sent to sre `{{ {{@}} }}`miraheze.org and we will respond in due course.
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:GHSA/Written_Security_Disclosure_Template
+**Source**: [https://meta.miraheze.org/wiki/Tech:GHSA/Written_Security_Disclosure_Template](https://meta.miraheze.org/wiki/Tech:GHSA/Written_Security_Disclosure_Template)
diff --git a/content/tech-docs/Tech:GHSA.md b/content/tech-docs/Tech:GHSA.md
@@ -80,4 +80,4 @@ If you need to create an advisory, follow the steps below:
 [Category:Guides for sysadmins](https://meta.miraheze.org/wiki/Category:Guides_for_sysadmins)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:GHSA
+**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
@@ -99,4 +99,4 @@ mediawiki is the repository that manages the MediaWiki source code, skins, and e
 [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:GitHub
+**Source**: [https://meta.miraheze.org/wiki/Tech:GitHub](https://meta.miraheze.org/wiki/Tech:GitHub)
diff --git a/content/tech-docs/Tech:Goals.md b/content/tech-docs/Tech:Goals.md
@@ -38,4 +38,4 @@ Site Reliability Engineering tasks being considered for a goal are left at the d
 | July - December 2022 | 7 | 6 | 1 | 86% |
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Goals
+**Source**: [https://meta.miraheze.org/wiki/Tech:Goals](https://meta.miraheze.org/wiki/Tech:Goals)
diff --git a/content/tech-docs/Tech:Grafana.md b/content/tech-docs/Tech:Grafana.md
@@ -15,4 +15,4 @@ This is done automatically on the first puppet run as Grafana configuration is h
 [Category:Monitoring services](https://meta.miraheze.org/wiki/Category:Monitoring_services)
 
 ----
-**Source**: https://meta.miraheze.org/wiki/Tech:Grafana
+**Source**: [https://meta.miraheze.org/wiki/Tech:Grafana](https://meta.miraheze.org/wiki/Tech:Grafana)