From 16f0ca120c6ace0ee5f78496307eddccebb24319 Mon Sep 17 00:00:00 2001 From: Universal-Omega Date: Tue, 17 Sep 2024 21:11:28 +0000 Subject: [PATCH] Auto-update Tech namespace pages 2024-09-17 21:11:28.707445 --- content/tech-docs/Tech:GitHub.md | 90 +++++++++++-------- content/tech-docs/Tech:On-Off_Boarding.md | 32 ++++--- ...Organization-Infrastructure_Specialists.md | 47 ++++++++++ ...ech:Organization-MediaWiki_Specialists.md} | 34 ++++--- ...ganization-Site_Reliability_Engineering.md | 44 --------- content/tech-docs/Tech:Organization.md | 4 + content/tech-docs/Tech:Server_admin_log.md | 24 +++++ content/tech-docs/Tech:Varnish.md | 10 ++- content/tech-docs/Tech:Volunteers-Chart.md | 20 ++++- content/tech-docs/Tech:Volunteers-List.md | 1 + content/tech-docs/Tech:Volunteers-bn.md | 2 + content/tech-docs/Tech:Volunteers-de.md | 4 + content/tech-docs/Tech:Volunteers-el.md | 2 + content/tech-docs/Tech:Volunteers-en.md | 4 + content/tech-docs/Tech:Volunteers-es.md | 4 + content/tech-docs/Tech:Volunteers-fi.md | 2 + content/tech-docs/Tech:Volunteers-fr.md | 4 + content/tech-docs/Tech:Volunteers-hi.md | 4 + content/tech-docs/Tech:Volunteers-id.md | 4 + content/tech-docs/Tech:Volunteers-ja.md | 4 + content/tech-docs/Tech:Volunteers-pt-br.md | 2 + content/tech-docs/Tech:Volunteers-scn.md | 2 + content/tech-docs/Tech:Volunteers-sv.md | 2 + content/tech-docs/Tech:Volunteers-tr.md | 4 + content/tech-docs/Tech:Volunteers-ur.md | 2 + content/tech-docs/Tech:Volunteers-zh-hans.md | 2 + content/tech-docs/Tech:Volunteers-zh-hant.md | 2 + content/tech-docs/Tech:Volunteers-zh-hk.md | 4 + content/tech-docs/Tech:Volunteers.md | 8 +- 29 files changed, 255 insertions(+), 113 deletions(-) create mode 100644 content/tech-docs/Tech:Organization-Infrastructure_Specialists.md rename content/tech-docs/{Tech:Organization-mw-admins.md => Tech:Organization-MediaWiki_Specialists.md} (50%) delete mode 100644 content/tech-docs/Tech:Organization-Site_Reliability_Engineering.md diff --git a/content/tech-docs/Tech:GitHub.md b/content/tech-docs/Tech:GitHub.md index 07b45ed82..2f9e0cc30 100644 --- a/content/tech-docs/Tech:GitHub.md +++ b/content/tech-docs/Tech:GitHub.md @@ -2,40 +2,44 @@ 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). +**GitHub** is the service we use to host our open-source repositories. They can be found [here](https://github.com/miraheze). -Push access to the repositories is limited to [system administrators](/tech-docs/techvolunteers), 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](/tech-docs/techvolunteers). It is recommended to read the "README.md" file for a repository before contributing to it. +Push access to the repositories is limited to [Technology team members](/tech-docs/techvolunteers), 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 member of the Technology team with access. Some repositories can also be deployed with [mwdeploy](/tech-docs/techmwdeploy). + +It is recommended to read the "README.md" file for a repository before contributing to it. + +Some repositories may be given access to Technology team members without shell access, however, only those with shell access may be given push access to repositories that automatically deploy (puppet, mw-config, mediawiki-repos, ssl, dns, and MirahezeMagic) ## Production repositories ### puppet -Puppet is the repository that manages all services/servers. -* **Push Access**: [Site Reliability Engineers (Infrastructure)](/tech-docs/techorganization#team-infrastructure-site-reliability-engineering) +[puppet](https://github.com/miraheze/puppet) is the repository that manages all services/servers. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist) * **Servers**: [puppet181](/tech-docs/techpuppet181) ### mw-config -mw-config (MediaWiki configuration) is the repository that manages settings for MediaWiki. -* **Push Access**: [Site Reliability Engineers (Infrastructure)](/tech-docs/techorganization#team-infrastructure-site-reliability-engineering), [MediaWiki Engineers](/tech-docs/techorganization#team-mediawiki-site-reliability-engineering) -* **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) +[mw-config](https://github.com/miraheze/mw-config) (MediaWiki configuration) is the repository that manages settings for MediaWiki. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist) +* **Servers**: MediaWiki servers -### mediawiki +### mediawiki-repos -mediawiki is the repository that manages the MediaWiki source code, skins, and extensions. -* **Push Access**: [Site Reliability Engineers (Infrastructure)](/tech-docs/techorganization#team-infrastructure-site-reliability-engineering), [MediaWiki Engineers](/tech-docs/techorganization#team-mediawiki-site-reliability-engineering) -* **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-repos](https://github.com/miraheze/mediawiki-repos) is the repository where we have a list of all installed extensions. Puppet uses this to clone the extension repos. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist) +* **Servers**: [mwtask171](/tech-docs/techmwtask171), [mwtask181](/tech-docs/techmwtask181), [test151](/tech-docs/techtest151) ### dns -[DNS](/tech-docs/techdns) (Domain Name System) is the repository that manages all DNS for Miraheze. -* **Push Access**: [Site Reliability Engineers (Infrastructure)](/tech-docs/techorganization#team-infrastructure-site-reliability-engineering) +[dns](https://github.com/miraheze/dns) is the repository that manages all [DNS](/tech-docs/techdns) (Domain Name System) for Miraheze. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist) * **Servers**: [ns1](/tech-docs/techns1), [ns2](/tech-docs/techns2) ### ssl -[SSL](/tech-docs/techssl_certificates) (Secure Sockets Layer) is the repository that manages all SSL certificates for Miraheze. -* **Push Access**: [Site Reliability Engineers (Infrastructure)](/tech-docs/techorganization#team-infrastructure-site-reliability-engineering), ssl-admins +[ssl](https://github.com/miraheze/ssl) is the repository that manages all [SSL certificates](/tech-docs/techssl_certificates) (Secure Sockets Layer) for Miraheze. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), ssl-admins * **Servers**: [puppet181](/tech-docs/techpuppet181) ## MediaWiki extensions and skins @@ -43,55 +47,67 @@ mediawiki is the repository that manages the MediaWiki source code, skins, and e ### 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 (*reference:* Currently [@translatewiki](https://github.com/translatewiki) only) -* **Servers**: MediaWiki servers (*reference:* Only if the extension is updated using [mwdeploy](/tech-docs/techmwdeploy) or manually) +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n (*reference:* Currently [@translatewiki](https://github.com/translatewiki) only) +* **Servers**: MediaWiki servers (*reference:* Only if the extension is updated using [mwdeploy](/tech-docs/techmwdeploy).) -### ManageWiki +### GlobalNewFiles -[ManageWiki](https://github.com/miraheze/ManageWiki) is a MediaWiki extension to manage the state of the wikis on Miraheze. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +[GlobalNewFiles](https://github.com/miraheze/GlobalNewFiles) is a MediaWiki extension that provides a [special page](https://meta.miraheze.org/wiki/Special:GlobalNewFiles) to display all newly uploaded files globally. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers -### WikiDiscover +### ImportDump -[WikiDiscover](https://github.com/miraheze/WikiDiscover) is a MediaWiki extension to create an [on-wiki list](https://meta.miraheze.org/wiki/Special:WikiDiscover) of Miraheze wikis. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +[ImportDump](https://github.com/miraheze/ImportDump) is a MediaWiki extension designed to automate user import requests. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers ### IncidentReporting [IncidentReporting](https://github.com/miraheze/IncidentReporting) is a MediaWiki extension that provides MediaWiki-based incident reporting forms. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n +* **Servers**: MediaWiki servers + +### ManageWiki + +[ManageWiki](https://github.com/miraheze/ManageWiki) is a MediaWiki extension to manage the state of the wikis on Miraheze. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers ### MatomoAnalytics [MatomoAnalytics](https://github.com/miraheze/MatomoAnalytics) is a MediaWiki extension for integration with Matomo for analytics. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers -### RottenLinks +### MirahezeMagic -[RottenLinks](https://github.com/miraheze/RottenLinks) is a MediaWiki extension for Rotten link detection. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +[MirahezeMagic](https://github.com/miraheze/MirahezeMagic) is a MediaWiki extension for Miraheze-specific i18n and hooks. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), i18n +* **Servers**: MediaWiki servers (*reference:* Extension is automatically updated by [mwdeploy](/tech-docs/techmwdeploy) whenever Puppet runs.) + +### RemovePII + +[RemovePII](https://github.com/miraheze/RemovePII) is a MediaWiki extension used by [trust and safety](https://meta.miraheze.org/wiki/Trust_and_Safety) to remove all personal identifiable information from a user. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers -### GlobalNewFiles +### RequestSSL -[GlobalNewFiles](https://github.com/miraheze/GlobalNewFiles) is a MediaWiki extension that provides a [special page](https://meta.miraheze.org/wiki/Special:GlobalNewFiles) to display all newly uploaded files globally. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +[RequestSSL](https://github.com/miraheze/RequestSSL) is a MediaWiki extension designed to facilitate user SSL requests for custom domains. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers -### RemovePII +### RottenLinks -[RemovePII](https://github.com/miraheze/RemovePII) is a MediaWiki extension used by [trust and safety](https://meta.miraheze.org/wiki/Trust_and_Safety) to remove all personal identifiable information from a user. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +[RottenLinks](https://github.com/miraheze/RottenLinks) is a MediaWiki extension for Rotten link detection. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers -### ImportDump +### WikiDiscover -[ImportDump](https://github.com/miraheze/ImportDump) is a MediaWiki extension designed to automate user import requests. -* **Push Access**: Site Reliability Engineers (Infrastructure), MediaWiki Engineers, i18n +[WikiDiscover](https://github.com/miraheze/WikiDiscover) is a MediaWiki extension to create an [on-wiki list](https://meta.miraheze.org/wiki/Special:WikiDiscover) of Miraheze wikis. +* **Push Access**: [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist), [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist), [Software Engineers](/tech-docs/techorganization#software-engineer), i18n * **Servers**: MediaWiki servers ## References diff --git a/content/tech-docs/Tech:On-Off_Boarding.md b/content/tech-docs/Tech:On-Off_Boarding.md index cb2498e9c..ec72873ff 100644 --- a/content/tech-docs/Tech:On-Off_Boarding.md +++ b/content/tech-docs/Tech:On-Off_Boarding.md @@ -15,6 +15,7 @@ This section is generic to all shell requests. ### Google Workspace * Add a Google Workspace account for the user. + * *This service requires 2FA and accounts are automatically suspended if it is not enabled within 24 hours of creation.* A valid wikitide.org email must exist for access on file. Please make sure to add a backup email and list the users' manager. On off boarding, this access must be suspended. You should manually check search console for delegated access. This may need Owner rights. If a linked device is stolen, devices may be banned from the devices section of the admin portal rather than suspending an account. ### IRC @@ -34,9 +35,14 @@ This section is generic to all shell requests. * #miraheze-feed-login (+AORefiorstv) * On off-boarding, +V should be taken away. Ops access can stay in non-confidential channels if the user is trustworthy. +### Discord + +* The user should be added to the appropriate roles on [Discord](https://meta.miraheze.org/wiki/Discord). + * These roles must be removed on off-boarding. + ### GitHub -* The user should be added to the relevant team in the GitHub account (usually mw-admins) which then provides sufficient access to push commits to the repositories they need to fulfil their role. +* The user should be added to the relevant team in the GitHub account (I.E. MediaWiki Specialists) which then provides sufficient access to push commits to the repositories they need to fulfil their role. * Access must be revoked on off-boarding, no exceptions. ### LDAP @@ -50,12 +56,12 @@ This section is generic to all shell requests. * New MediaWiki Specialists or Infrastructure Specialists being on-boarded should be given adminship to Grafana. * Access must be revoked on off-boarding, no exceptions. -## Graylog +### Graylog * New MediaWiki Specialists or Infrastructure Specialists must receive access to Graylog. MediaWiki Specialists: grant Reader role only, you should share access to the MediaWiki related streams in Graylog. Infrastructure Specialist: grant Admin role. * Access must be revoked on off-boarding, no exceptions. -## Matomo +### Matomo * The user may be provided access to [Matomo](https://analytics.wikitide.net/index.php?module=UsersManager), our analytics platform. There are separate groups for MediaWiki Specialists or Infrastructure Specialists. * On off-boarding, this should be revoked by default, although there may be legitimate reasons to keep access. @@ -77,19 +83,24 @@ This section is generic to all shell requests. * If the user wishes, and is eligible under the [access policy](https://meta.miraheze.org/wiki/Phorge#Access_Policy), grant Phorge administrator. * Must be revoked on off-boarding. +### Mattermost + +* The user should be invited to Mattermost and added to the channels as mentioned on [Tech:Mattermost](/tech-docs/techmattermost). + * On off-boarding the user account should be disabled, unless they are (and are remaining) a member of the [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) or [Trust and Safety](https://meta.miraheze.org/wiki/Trust_and_Safety). + ## Wikis -* For MediaWiki Specialists, the global system administrator group may be useful - it is, however, not a strict requirement. +* For MediaWiki Specialists, the global Technology team group may be useful - it is, however, not a strict requirement. * On off-boarding, any access to global groups or technical wikis must be revoked if it was for being a volunteer with shell or privileged access. * Access to staffwiki can be granted to users holding shell access. - * On off-boarding, this group must be revoked (both on-wiki and in LocalSettings.php), unless the user is also a Board member. In said case, please do not remove those groups. + * On off-boarding, this group must be revoked (both on-wiki and in LocalSettings.php), unless the user is also a member of the Board of Directors. In said case, please do not remove from staffwiki. ## Social Media ### Twitter * If a new system administrator wishes, they may request access to the @miraheze and @MirahezeStatus Twitter accounts. - * Access to the Twitter accounts should be revoked on off-boarding, unless the user intends to keep managing social media and is trustworthy enough. Use your judgement. `{{ {{note|TweetDeck situation:}} }}` As of writing, TweetDeck seems not to be available to volunteers in all regions due to new Twitter policies. The account for the Twitter password must only be shared with Technology team members who demonstrate a clear need for such access. + * Access to the Twitter accounts should be revoked on off-boarding, unless the user intends to keep managing social media and is trustworthy enough. Use your judgement. `{{ {{note|TweetDeck situation:}} }}` As of writing, TweetDeck seems not to be available to volunteers in all regions due to new Twitter policies. The account for the Twitter password must only be shared with Technology team members or members of the Board of Directors who demonstrate a clear need for such access. ### Facebook @@ -105,6 +116,11 @@ The above applies, this section covers things which are specific to Infrastructu * Basic access to the account for ticketing purposes and the 'operations back door' should be granted. This should be so any operations member can fulfil their duties on their own. * Access must be revoked on off-boarding, no exceptions. +### Proxmox + +* Infrastructure Specialists with Operations-level access should be given access to [Proxmox](/tech-docs/techproxmox) and ensure that they can properly login. + * Access must be revoked on off-boarding, no exceptions. + ### iDRAC * Infrastructure Specialists with Operations-level access should be given access to iDRAC on all the cloud servers and ensure that they can properly login. @@ -114,10 +130,6 @@ The above applies, this section covers things which are specific to Infrastructu * Infrastructure Specialists should be talked through how private git works and how to access and commit things to it. This is granted through root on puppet181 and no specific access is necessary besides puppet181 root. -## Google Services - -*This service requires 2FA and accounts are automatically suspended if it is not enabled within 24 hours of creation.* A valid wikitide.org email must exist for access on file. Please make sure to add a backup email and list the users' manager. On off boarding, this access must be suspended. You should manually check search console for delegated access. This may need Owner rights. If a linked device is stolen, devices may be banned from the devices section of the admin portal rather than suspending an account. - ## Categories * [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech) diff --git a/content/tech-docs/Tech:Organization-Infrastructure_Specialists.md b/content/tech-docs/Tech:Organization-Infrastructure_Specialists.md new file mode 100644 index 000000000..59f47ddff --- /dev/null +++ b/content/tech-docs/Tech:Organization-Infrastructure_Specialists.md @@ -0,0 +1,47 @@ +--- +title: Tech:Organization/Infrastructure Specialists +--- + +This is a guide for all [Infrastructure Specialists](/tech-docs/techorganization#infrastructure-specialist). They have access to all servers and GitHub repositories (see [Tech:Volunteers](/tech-docs/techvolunteers)), and they are responsible for maintaining all servers and internal infrastructure and making sure they function smoothly. + +## Rules + + *See also: [Tech:Conduct Policy](/tech-docs/techconduct_policy)* + +* Be respectful to other volunteers and users. You represent the Miraheze project. +* Don't suddenly change big parts of the infrastructure (MediaWiki, Varnish, Bacula, etc.) (e.g., way how things are done in the current style) without discussing it with the other members of the Technology team. +* Be **VERY** careful when manipulating sensitive data (such as db* or nfs*) as it could lead to data loss. +* Don't use the servers for unrelated purposes. +* Don't put abnormally high load(s) on the server(s) if avoidable. ([Grafana](/tech-docs/techgrafana) can be used for more details). +* Respect privacy. Don't publish access logs, IP addresses, content of private wikis, or other personally identifiable information. If in doubt, ask before publishing. Publishing any such content is likely to be a violation of your non-disclosure agreement (NDA) with the WikiTide Foundation. +* Don't publish database passwords, private keys, etc as well. + `{{ {{note}} }}` Violation of these rules can result in warnings or revocation of access. + +## Deployment + +* When deploying a change (SSL certificate, database rename, etc.), you are **required** to closely watch the change going live. +* After committing a change to any repo (and being sure it should work), run `sudo puppet agent -tv` on the server involved. It can take a while before the change is actually deployed. +* Watch the error logs: [#Monitoring errors](#monitoring-errors). + +*Further specifics to be filled in by Technology team* + +## Monitoring errors + +Follow the instructions at [Tech:Graylog](/tech-docs/techgraylog) for most errors. + +## Debugging + +* Look at the [error logs](#monitoring-errors). +* Either use the [WikiTideDebug](https://github.com/miraheze/WikiTideDebug) extension for Chrome or try to send the failing HTTP request to one of the MediaWiki servers with the header `X-WikiTide-Debug: (mw1[5678][1234]|test151|mwtask1[5678]1).wikitide.net` (replace with the desired server), it could be an error that is cached in [Varnish](/tech-docs/techvarnish) or [Cloudflare](/tech-docs/techcloudflare). + * `X-WikiTide-Debug` also requires an access key sent via `X-WikiTide-Debug-Access-Key`, unless the request is made from a server from our own internal infrastructure (from one of our own IP ranges). If you don't have this access key, please ask another member of the Technology team. + +## See also + +* [MediaWiki Specialists guide](https://meta.miraheze.org/wiki/Tech:Organization/MediaWiki_Specialists) + +## Categories + +* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides) + +---- +**[Go to Source →](https://meta.miraheze.org/wiki/Tech:Organization/Infrastructure_Specialists)** \ No newline at end of file diff --git a/content/tech-docs/Tech:Organization-mw-admins.md b/content/tech-docs/Tech:Organization-MediaWiki_Specialists.md similarity index 50% rename from content/tech-docs/Tech:Organization-mw-admins.md rename to content/tech-docs/Tech:Organization-MediaWiki_Specialists.md index f2371350b..5f17e9ff8 100644 --- a/content/tech-docs/Tech:Organization-mw-admins.md +++ b/content/tech-docs/Tech:Organization-MediaWiki_Specialists.md @@ -1,32 +1,35 @@ --- -title: Tech:Organization/mw-admins +title: Tech:Organization/MediaWiki Specialists --- -This is a guide for all MediaWiki admins. MediaWiki admins have access to Miraheze 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), [mwtask171](/tech-docs/techmwtask171), [mwtask181](/tech-docs/techmwtask181), [test151](/tech-docs/techtest151), and [jobchron171](/tech-docs/techjobchron171). +This is a guide for all [MediaWiki Specialists](/tech-docs/techorganization#mediawiki-specialist). MediaWiki Specialists have access to servers: [mw151](/tech-docs/techmw151), [mw152](/tech-docs/techmw152), [mw153](https://meta.miraheze.org/wiki/Tech:Mw153), [mw154](https://meta.miraheze.org/wiki/Tech:Mw154), [mw161](/tech-docs/techmw161), [mw162](/tech-docs/techmw162), [mw163](https://meta.miraheze.org/wiki/Tech:Mw163), [mw164](https://meta.miraheze.org/wiki/Tech:Mw164), [mw171](/tech-docs/techmw171), [mw172](/tech-docs/techmw172), [mw173](https://meta.miraheze.org/wiki/Tech:Mw173), [mw174](https://meta.miraheze.org/wiki/Tech:Mw174), [mw181](/tech-docs/techmw181), [mw182](/tech-docs/techmw182), [mw183](https://meta.miraheze.org/wiki/Tech:Mw183), [mw184](https://meta.miraheze.org/wiki/Tech:Mw184), [mwtask151](https://meta.miraheze.org/wiki/Tech:Mwtask151), [mwtask161](https://meta.miraheze.org/wiki/Tech:Mwtask161), [mwtask171](/tech-docs/techmwtask171), [mwtask181](/tech-docs/techmwtask181), [test151](/tech-docs/techtest151), and [jobchron171](/tech-docs/techjobchron171) -In case of any doubts regarding a command or configuration change, mw-admins should ask either another mw-admin, or Site Reliability Engineering before going through with it. In addition, mw-admins should test any new changes on test151 before adding them to production. +In case of any doubts regarding a command or configuration change, MediaWiki Specialists should ask either another member of the [Technology team](/tech-docs/techvolunteers) before going through with it. In addition, MediaWiki Specialists should test any new changes on test151 before adding them to production. ## Rules -* Be respectful to other volunteers and users. You represent the Miraheze project. -* Don't suddenly change big parts of the MediaWiki infrastructure (e.g., way how things are done in the current style) without discussing it with the other sysadmins. -* Don't use the servers for non-Miraheze purposes. + *See also: [Tech:Conduct Policy](/tech-docs/techconduct_policy)* + +* Be respectful to other volunteers and users. You represent the project. +* Don't suddenly change big parts of the MediaWiki infrastructure (e.g., way how things are done in the current style) without discussing it with the other members of the Technology team. +* Don't use the servers for unrelated purposes. * Don't put abnormally high load(s) on the server(s) if avoidable. ([Grafana](/tech-docs/techgrafana) can be used for more details) -* Respect privacy. Don't publish access logs, IP addresses, content of private wikis, or other personally identifiable information. *If in doubt, ask before publishing. Publishing any such content is likely to be a violation of your non-disclosure agreement (NDA) with the WikiTide Foundation, or Miraheze Limited if your NDA predates the merger.* +* Respect privacy. Don't publish access logs, IP addresses, content of private wikis, or other personally identifiable information. *If in doubt, ask before publishing. Publishing any such content is likely to be a violation of your non-disclosure agreement (NDA) with the WikiTide Foundation.* * Don't publish database passwords, private keys, etc as well. * When in doubt, ask questions first, act second. `{{ {{note}} }}` Violation of these rules can result in warnings or revocation of access. ## Maintenance scripts -* They should typically only be run on mwtask181 or mwtask171. +* They should typically only be run on an mwtask server. * Always run them as www-data (prefix command with `sudo -u www-data`). * Always `!log` maintenance script runs in #miraheze-tech-ops (unless you were running puppet or were using sql.php, and did **not** execute any queries that changed the database (e.g. SELECT/DESCRIBE queries) * You can optionally use the [mwscript](/tech-docs/techmediawiki_appserver#mwscript) wrapper to automatically log these. * If you need to run a script on all wikis, use the *foreachwikiindblist* wrapper: * `sudo -u www-data /usr/local/bin/foreachwikiindblist /srv/mediawiki/cache/databases.json /srv/mediawiki//maintenance/yourscript.php --put-your-parameters --here` -* update.php is evil. If you need to run it while you're not doing a MediaWiki upgrade, then something is really wrong. - * maintenance/update.php just automatically creates all required database tables on the wiki(s) it is run on. SQL files should be added to the CreateWiki config setting so that tables are automatically added to all new wikis. See [Tech:Adding a new extension](/tech-docs/techadding_a_new_extension) for enabling extensions or adding tables to existing wikis. +* update.php is evil. It should absolutely never be ran in production. + * SQL files should be added to the CreateWiki config setting so that tables are automatically added to all new wikis. See [Tech:Adding a new extension](/tech-docs/techadding_a_new_extension) for enabling extensions or adding tables to existing wikis. + ### Accessing the mhglobal database If you need to do work on the `mhglobal` database (where the CentralAuth and OATHAuth tables are, among others), but you don't have access to the db* servers, the recommended way is to run `sql.php` with `loginwiki` as the wiki and give it the `--wikidb=mhglobal` option. You'll then have access to `mhglobal`. @@ -39,7 +42,8 @@ See [Tech:Adding a new extension](/tech-docs/techadding_a_new_extension). * Ensure the PHP syntax is correct, you want to avoid deploying files with syntax errors. * Although everyone makes mistakes sometimes, try to avoid them in the first place and be aware of how the changes you make can affect the entire site. - * If a syntax error should occur, push a fixing-commit to the repo(s) and manually run puppet (`sudo puppet agent -t`) on mwtask181. + * If a syntax error should occur, push a fixing-commit to the repo(s) and manually run [mwdeploy](/tech-docs/techmwdeploy) or [puppet](/tech-docs/techpuppet) (`sudo puppet agent -tv`) on mwtask181. + * The CIs will almost always cache the more simple syntax errors as well, so it is recommended to let those finish before pushing commits. * When a configuration variable is changed, you should be completely aware what it does, and how it could impact a wiki security-wise. * There is more stuff in LocalSettings.php than just configuration variables, like [this](https://github.com/miraheze/mw-config/blob/d9b720ba7a19fd77d7dc7c08a9e3f640cb6c9b0f/LocalSettings.php#L2905-L3028). You are allowed to edit such stuff, but if you are not familiar with its functionality, it's not recommended to touch it (or to merge pull requests that make changes to this area). See [#Deployment](#deployment) for the rest. @@ -47,7 +51,7 @@ See [#Deployment](#deployment) for the rest. ## Deployment * When deploying a configuration change or extension, you are **required** to closely watch the change going live. -* After committing a change to the mediawiki or mw-config repo (and being sure it should work), run `sudo puppet agent -t` on mwtask181. It can take a while before the change is actually deployed. +* After committing a change to the mediawiki or mw-config repo (and being sure it should work), run `mwdeploy --config --pull=config --servers=all --versions=all` or `sudo puppet agent -tv` on mwtask181. It can take up to 30 minutes before the change is actually deployed automatically. * Watch the error logs: [#Monitoring errors](#monitoring-errors). ## Monitoring errors @@ -57,11 +61,13 @@ Follow the instructions at [Tech:Graylog](/tech-docs/techgraylog). ## Debugging * Look at the [error logs](#monitoring-errors). -* Try to send the failing HTTP request to one of the mw servers with the header `X-Miraheze-Debug: (mw1[5678][12]|test151|mwtask181).wikitide.net` (replace with the desired server), it could be an error that is cached in Varnish. +* Either use the [WikiTideDebug](https://github.com/miraheze/WikiTideDebug) extension for Chrome or try to send the failing HTTP request to one of the MediaWiki servers with the header `X-WikiTide-Debug: (mw1[5678][1234]|test151|mwtask1[5678]1).wikitide.net` (replace with the desired server), it could be an error that is cached in [Varnish](/tech-docs/techvarnish) or [Cloudflare](/tech-docs/techcloudflare). + * `X-WikiTide-Debug` also requires an access key sent via `X-WikiTide-Debug-Access-Key`, unless the request is made from a server from our own internal infrastructure (from one of our own IP ranges). If you don't have this access key, please ask another member of the Technology team. +* You can also use the [MediaWikiDebugJS](https://github.com/miraheze/MediaWikiDebugJS) extension for Chrome to debug MediaWiki response times, or what backend MediaWiki and/or cache proxy servers you are connecting to. ## Categories * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides) ---- -**[Go to Source →](https://meta.miraheze.org/wiki/Tech:Organization/mw-admins)** \ No newline at end of file +**[Go to Source →](https://meta.miraheze.org/wiki/Tech:Organization/MediaWiki_Specialists)** \ No newline at end of file diff --git a/content/tech-docs/Tech:Organization-Site_Reliability_Engineering.md b/content/tech-docs/Tech:Organization-Site_Reliability_Engineering.md deleted file mode 100644 index 403bcbec3..000000000 --- a/content/tech-docs/Tech:Organization-Site_Reliability_Engineering.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Tech:Organization/Site Reliability Engineering ---- - -This is a guide for all Miraheze Site Reliability Engineers. They have access to Miraheze servers and to Miraheze GitHub repositories (see [Tech:Volunteers](/tech-docs/techvolunteers)), and they are responsible for maintaining all Miraheze servers and making sure they function smoothly. - -## Rules - -* Be respectful to other volunteers and users. You represent the Miraheze project. -* Don't suddenly change big parts of the infrastructure (MediaWiki, Varnish, Bacula, etc.) (e.g., way how things are done in the current style) without discussing it with the other site reliability engineers (and any sysadmins). -* Be **VERY** careful when manipulating sensitive data (such as db* or nfs*) as it could lead to data loss. -* Don't use the servers for non-Miraheze purposes. -* Don't put abnormally high load(s) on the server(s) if avoidable. ([Grafana](/tech-docs/techgrafana) can be used for more details). -* Respect privacy. Don't publish access logs, IP addresses, content of private wikis, or other personally identifiable information. If in doubt, ask before publishing. -* Don't publish database passwords, private keys, etc as well. - `{{ {{note}} }}` Violation of these rules can result in warnings or revocation of access. - -## Deployment - -* When deploying a change (SSL certificate, database rename, etc.), you are **required** to closely watch the change going live. -* After committing a change to any repo (and being sure it should work), run `sudo puppet agent -tv` on the server involved. It can take a while before the change is actually deployed. -* Watch the error logs: [#Monitoring errors](#monitoring-errors). - -*Further specifics to be filled in by SRE* - -## Monitoring errors - -*To be filled in for specific servers* - -## Debugging - -* Look at the [error logs](#monitoring-errors). -* Try to send the failing HTTP request with the header `X-WikiTide-Debug: 1`, it could be an error that is cached in Varnish. - -## See also - -* [mw-admins guide](/tech-docs/techorganization-mw-admins) - -## Categories - -* [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides) - ----- -**[Go to Source →](https://meta.miraheze.org/wiki/Tech:Organization/Site_Reliability_Engineering)** \ No newline at end of file diff --git a/content/tech-docs/Tech:Organization.md b/content/tech-docs/Tech:Organization.md index 3fe978e38..28315d7c2 100644 --- a/content/tech-docs/Tech:Organization.md +++ b/content/tech-docs/Tech:Organization.md @@ -48,10 +48,14 @@ Project Managers triage incoming support requests from the community, within the ### MediaWiki Specialist + *See also: [Tech:Organization/MediaWiki Specialists](https://meta.miraheze.org/wiki/Tech:Organization/MediaWiki_Specialists)* + MediaWiki Specialists are responsible for maintaining the MediaWiki core platform and extensions, including in-house extensions. They operate the latest stable version of MediaWiki, manage configuration and feature requests from the community, and work with upstream and third-party MediaWiki developers. ### Infrastructure Specialist + *See also: [Tech:Organization/Infrastructure Specialists](https://meta.miraheze.org/wiki/Tech:Organization/Infrastructure_Specialists)* + Infrastructure Specialists ensure Miraheze's services and servers are fast, reliable and secure. Infrastructure Specialists are responsible for providing the critical services that support our deployment of MediaWiki, including virtual and physical servers, relational databases, media storage, automation tooling, configuration management systems, networking, continuous integration and continuous delivery, cache stores, and observability platforms. Infrastructure Specialists are expected to monitor and maintain a wide range of software and services, ensuring the uptime of the wider cluster. They take control during incidents and working as a team to mitigate, resolve, and prevent future outages. diff --git a/content/tech-docs/Tech:Server_admin_log.md b/content/tech-docs/Tech:Server_admin_log.md index 01ec3b1eb..a1f06218d 100644 --- a/content/tech-docs/Tech:Server_admin_log.md +++ b/content/tech-docs/Tech:Server_admin_log.md @@ -2,6 +2,30 @@ title: Tech:Server admin log --- +## 2024-09-17 + +* 18:02 MirahezeLSBot: [@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 28s +* 18:01 MirahezeLSBot: [@mwtask181] starting deploy of {'config': True} to all +* 17:53 MirahezeLSBot: [@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s +* 17:53 MirahezeLSBot: [@test151] starting deploy of {'config': True} to test151 +* 17:37 MirahezeLSBot: [@mwtask171] finished deploy of {'config': True} to all - SUCCESS in 25s +* 17:37 MirahezeLSBot: [@mwtask171] starting deploy of {'config': True} to all +* 16:53 MirahezeLSBot: [@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s +* 16:53 MirahezeLSBot: [@test151] starting deploy of {'config': True} to test151 +* 16:37 MirahezeLSBot: [@mwtask171] finished deploy of {'config': True} to all - SUCCESS in 28s +* 16:37 MirahezeLSBot: [@mwtask171] starting deploy of {'config': True} to all +* 16:33 MirahezeLSBot: [@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 27s +* 16:32 MirahezeLSBot: [@mwtask181] starting deploy of {'config': True} to all +* 15:57 Reception123: salt-ssh -E 'mw.*' cmd.run 'sudo -u www-data /usr/local/bin/foreachwikiindblist /srv/mediawiki/cache/databases.json /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/extensions/MirahezeMagic/maintenance/resetWikiCaches.php' (again) +* 15:45 MirahezeLSBot: [reception@mwtask181] sudo -u www-data php /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/maintenance/deleteBatch.php --wiki=metawiki /home/reception/forcedelmeta.txt --r=issue with deletion (END - exit=0) +* 15:45 MirahezeLSBot: [reception@mwtask181] sudo -u www-data php /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/maintenance/deleteBatch.php --wiki=metawiki /home/reception/forcedelmeta.txt --r=issue with deletion (START) +* 10:59 MirahezeLSBot: [reception@mwtask181] finished deploy of {'l10n': True, 'lang': 'en', 'versions': '1.42', 'upgrade_extensions': 'CreateWiki'} to all - SUCCESS in 47s +* 10:59 MirahezeLSBot: [reception@mwtask181] starting deploy of {'l10n': True, 'lang': 'en', 'versions': '1.42', 'upgrade_extensions': 'CreateWiki'} to all +* 10:58 MirahezeLSBot: [reception@mwtask181] finished deploy of {'l10n': True, 'lang': 'en', 'versions': '1.42', 'upgrade_extensions': 'MirahezeMagic'} to all - SUCCESS in 25s +* 10:58 MirahezeLSBot: [reception@mwtask181] starting deploy of {'l10n': True, 'lang': 'en', 'versions': '1.42', 'upgrade_extensions': 'MirahezeMagic'} to all +* 10:58 MirahezeLSBot: [reception@mwtask181] finished deploy of {'l10n': True, 'lang': 'en', 'versions': '1.42', 'upgrade_extensions': 'MirahezeMagic'} to all - SUCCESS in 33s +* 10:57 MirahezeLSBot: [reception@mwtask181] starting deploy of {'l10n': True, 'lang': 'en', 'versions': '1.42', 'upgrade_extensions': 'MirahezeMagic'} to all + ## 2024-09-16 * 18:39 RhinosF1: added static.help.wikitide.net to cf dns diff --git a/content/tech-docs/Tech:Varnish.md b/content/tech-docs/Tech:Varnish.md index cae576d2a..5b68bb658 100644 --- a/content/tech-docs/Tech:Varnish.md +++ b/content/tech-docs/Tech:Varnish.md @@ -4,7 +4,7 @@ title: Tech:Varnish [Varnish](https://meta.miraheze.org/wiki/wikipedia:Varnish_(software)) is an HTTP cache proxy, which can serve almost anything (including articles) without asking the MediaWiki appservers. -Miraheze is currently migrating to [Cloudflare](/tech-docs/techcloudflare) as a replacement for Varnish. Varnish currently only serves traffic for wikis on *.wikitide.org/*.wikitide.net wikis and for wikis that use Miraheze's DNS nameservers. +Miraheze is currently migrating to [Cloudflare](/tech-docs/techcloudflare) as a replacement for Varnish. Varnish currently only serves traffic for domains on *.wikitide.org/*.wikitide.net and for custom domains that use Miraheze's DNS nameservers. ## Basics @@ -57,9 +57,13 @@ cp26 is the cache proxy who served the request, HIT indicates the request was se ***Note: due to [a bug in Varnish](https://www.varnish-cache.org/trac/ticket/1492), obj.hits won't be reset after a ban was applied.*** -### X-Miraheze-Debug +### X-WikiTide-Debug -Using the `X-Miraheze-Debug` header, you can force the request to be passed to a certain backend. For example, requests with the header `X-Miraheze-Debug: test151.wikitide.net` will always be passed (regardless of whether it could be served from the cache or not) to test151. +Using the `X-WikiTide-Debug` header, you can force the request to be passed to a certain backend. For example, requests with the header `X-WikiTide-Debug: test151.wikitide.net` will always be passed (regardless of whether it could be served from the cache or not) to test151. + +`X-WikiTide-Debug` also requires an access key sent via `X-WikiTide-Debug-Access-Key`, unless the request is made from a server from our own internal infrastructure (from one of our own IP ranges). If you don't have this access key, please ask another member of the [Technology team](/tech-docs/techvolunteers). + +You can also use the [WikiTideDebug](https://github.com/miraheze/WikiTideDebug) Chrome extension to proxy servers directly from your browser. ## One-off purges (bans) diff --git a/content/tech-docs/Tech:Volunteers-Chart.md b/content/tech-docs/Tech:Volunteers-Chart.md index b6ee20a03..ea5f80f78 100644 --- a/content/tech-docs/Tech:Volunteers-Chart.md +++ b/content/tech-docs/Tech:Volunteers-Chart.md @@ -41,7 +41,7 @@ PlotData = color:previous from:30/03/2023 till:09/05/2023 text:"[[User:OrangeStar|OrangeStar]]" color:current from:06/01/2024 till:end text:"[[User:Original Authority|Original Authority]]" color:previous from:03/01/2024 till:20/02/2024 text:"[[User:Owen|Owen]]" - color:previous from:10/04/2018 till:13/06/2021 text:"[[User:Paladox|Paladox]]" + color:current from:10/04/2018 till:13/06/2021 text:"[[User:Paladox|Paladox]]" color:current from:03/08/2016 till:15/06/2023 text:"[[User:Reception123|Reception123]]" color:previous from:21/09/2015 till:05/07/2016 text:"[[User:Revi|Revi]]" color:previous from:10/09/2019 till:14/12/2019 text:"[[User:RhinosF1|RhinosF1]]" @@ -92,7 +92,7 @@ PlotData = barset:skip barset:skip barset:skip - color:previous from:09/08/2021 till:16/06/2023 text:"[[User:Paladox|Paladox]]" + color:current from:09/08/2021 till:16/06/2023 text:"[[User:Paladox|Paladox]]" barset:break barset:skip barset:skip @@ -106,13 +106,27 @@ PlotData = barset:skip barset:skip barset:skip - color:previous from:26/06/2023 till:20/02/2024 text:"[[User:Paladox|Paladox]]" + color:current from:26/06/2023 till:20/02/2024 text:"[[User:Paladox|Paladox]]" color:current from:02/01/2024 till:end text:"[[User:Reception123|Reception123]]" barset:skip barset:skip barset:skip barset:skip color:current from:02/01/2024 till:end text:"[[User:Universal Omega|Universal Omega]]" + barset:break + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + barset:skip + color:current from:17/09/2024 till:end text:"[[User:Paladox|Paladox]]" }} }} ``` diff --git a/content/tech-docs/Tech:Volunteers-List.md b/content/tech-docs/Tech:Volunteers-List.md index f0390fff1..70f8ba50f 100644 --- a/content/tech-docs/Tech:Volunteers-List.md +++ b/content/tech-docs/Tech:Volunteers-List.md @@ -10,6 +10,7 @@ title: Tech:Volunteers/List | [Harej](https://meta.miraheze.org/wiki/User:Harej)
*Project Manager* | None | harej `{{ {{@}} }}`miraheze.org | No | No | No | Yes | No | Yes | No | | [MacFan4000](https://meta.miraheze.org/wiki/User:MacFan4000)
*MediaWiki Specialist* | MacFan4000 | macfan `{{ {{@}} }}`miraheze.org | MediaWiki servers, puppet181 | MediaWiki Specialists; ssl-admins | No | No | Yes | No | No | | [Original Authority](https://meta.miraheze.org/wiki/User:Original_Authority)
*MediaWiki Specialist* | None | oa `{{ {{@}} }}`miraheze.org | MediaWiki servers, puppet181 | MediaWiki Specialists; ssl-admins | No | No | Yes | No | No | +| [Paladox](https://meta.miraheze.org/wiki/User:Paladox)
*Infrastructure Specialist* | paladox | paladox `{{ {{@}} }}`miraheze.org | Root on all servers | Owner | Yes | Yes | Yes | No | Yes | | [Reception123](https://meta.miraheze.org/wiki/User:Reception123)
*Deputy Director of Technology* | Reception123 | reception `{{ {{@}} }}`miraheze.org | Root on all servers | Owner | Yes | Yes | Yes | No | Yes | | [RhinosF1](https://meta.miraheze.org/wiki/User:RhinosF1)
*Software Engineer* | RhinosF1 | rhinosf1 `{{ {{@}} }}`miraheze.org | No | Software Engineers | No | No | Yes | No | No | | [TheresNoTime](https://meta.miraheze.org/wiki/User:TheresNoTime)
*MediaWiki Specialist* | TheresNoTime | theresnotime `{{ {{@}} }}`miraheze.org | MediaWiki servers | MediaWiki Specialists | No | No | No | No | No | diff --git a/content/tech-docs/Tech:Volunteers-bn.md b/content/tech-docs/Tech:Volunteers-bn.md index 622d018a7..7e091d634 100644 --- a/content/tech-docs/Tech:Volunteers-bn.md +++ b/content/tech-docs/Tech:Volunteers-bn.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! গ্রাফানা (অ্যাডমিন) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-de.md b/content/tech-docs/Tech:Volunteers-de.md index 3bde81714..c1888c91a 100644 --- a/content/tech-docs/Tech:Volunteers-de.md +++ b/content/tech-docs/Tech:Volunteers-de.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Grafik + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## Siehe auch * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-el.md b/content/tech-docs/Tech:Volunteers-el.md index 9564a380a..52bb62f9e 100644 --- a/content/tech-docs/Tech:Volunteers-el.md +++ b/content/tech-docs/Tech:Volunteers-el.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-en.md b/content/tech-docs/Tech:Volunteers-en.md index 8cc314afc..09f90fb07 100644 --- a/content/tech-docs/Tech:Volunteers-en.md +++ b/content/tech-docs/Tech:Volunteers-en.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-es.md b/content/tech-docs/Tech:Volunteers-es.md index 9c2125c7a..e741dd038 100644 --- a/content/tech-docs/Tech:Volunteers-es.md +++ b/content/tech-docs/Tech:Volunteers-es.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Gráfico + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## Véase también * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-fi.md b/content/tech-docs/Tech:Volunteers-fi.md index d3bd85759..4d3e9e2d4 100644 --- a/content/tech-docs/Tech:Volunteers-fi.md +++ b/content/tech-docs/Tech:Volunteers-fi.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (ylläpitäjä) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-fr.md b/content/tech-docs/Tech:Volunteers-fr.md index 4808a6301..bb7d69b9d 100644 --- a/content/tech-docs/Tech:Volunteers-fr.md +++ b/content/tech-docs/Tech:Volunteers-fr.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Tableau + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## Voir aussi * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-hi.md b/content/tech-docs/Tech:Volunteers-hi.md index f0572656c..8b787b721 100644 --- a/content/tech-docs/Tech:Volunteers-hi.md +++ b/content/tech-docs/Tech:Volunteers-hi.md @@ -23,6 +23,10 @@ title: Tech:Volunteers/hi ! Grafana (प्रबंधक) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### चार्ट + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## ये भी देखें * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-id.md b/content/tech-docs/Tech:Volunteers-id.md index 6f3febc43..eeee9b30a 100644 --- a/content/tech-docs/Tech:Volunteers-id.md +++ b/content/tech-docs/Tech:Volunteers-id.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Bagan + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## Lihat juga * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-ja.md b/content/tech-docs/Tech:Volunteers-ja.md index 6de05eba2..3a779ba9e 100644 --- a/content/tech-docs/Tech:Volunteers-ja.md +++ b/content/tech-docs/Tech:Volunteers-ja.md @@ -23,6 +23,10 @@ title: Tech:Volunteers/ja ! Grafana (管理者) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### チャート + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## 関連項目 * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-pt-br.md b/content/tech-docs/Tech:Volunteers-pt-br.md index bd97b4017..fee0c0950 100644 --- a/content/tech-docs/Tech:Volunteers-pt-br.md +++ b/content/tech-docs/Tech:Volunteers-pt-br.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-scn.md b/content/tech-docs/Tech:Volunteers-scn.md index 6b74240fd..dc2804fe1 100644 --- a/content/tech-docs/Tech:Volunteers-scn.md +++ b/content/tech-docs/Tech:Volunteers-scn.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-sv.md b/content/tech-docs/Tech:Volunteers-sv.md index 9596d35f1..c14bea55f 100644 --- a/content/tech-docs/Tech:Volunteers-sv.md +++ b/content/tech-docs/Tech:Volunteers-sv.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-tr.md b/content/tech-docs/Tech:Volunteers-tr.md index ba339bf81..f7b81ce16 100644 --- a/content/tech-docs/Tech:Volunteers-tr.md +++ b/content/tech-docs/Tech:Volunteers-tr.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Yönetici) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Geçmiş/Şimdiki SGM gönüllülerinin listesi + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## Ayrıca bakınız * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-ur.md b/content/tech-docs/Tech:Volunteers-ur.md index 206ae9de3..840e4e19e 100644 --- a/content/tech-docs/Tech:Volunteers-ur.md +++ b/content/tech-docs/Tech:Volunteers-ur.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! گرافانا (ایڈمن) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) diff --git a/content/tech-docs/Tech:Volunteers-zh-hans.md b/content/tech-docs/Tech:Volunteers-zh-hans.md index 30046b043..8b7a96148 100644 --- a/content/tech-docs/Tech:Volunteers-zh-hans.md +++ b/content/tech-docs/Tech:Volunteers-zh-hans.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana（管理员） |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## 参阅 * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-zh-hant.md b/content/tech-docs/Tech:Volunteers-zh-hant.md index 00ba8439d..944365e81 100644 --- a/content/tech-docs/Tech:Volunteers-zh-hant.md +++ b/content/tech-docs/Tech:Volunteers-zh-hant.md @@ -23,6 +23,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana（管理員） |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## 參閱 * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers-zh-hk.md b/content/tech-docs/Tech:Volunteers-zh-hk.md index a38166c56..11b4a06c9 100644 --- a/content/tech-docs/Tech:Volunteers-zh-hk.md +++ b/content/tech-docs/Tech:Volunteers-zh-hk.md @@ -23,6 +23,10 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana（管理員） |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### 圖表 + + `{{ {{:Tech:Volunteers/Chart}} }}` + ## 參閱 * [Tech:Organization](/tech-docs/techorganization) diff --git a/content/tech-docs/Tech:Volunteers.md b/content/tech-docs/Tech:Volunteers.md index 99e473275..bfedf3ba2 100644 --- a/content/tech-docs/Tech:Volunteers.md +++ b/content/tech-docs/Tech:Volunteers.md @@ -2,7 +2,9 @@ title: Tech:Volunteers --- - `{{ {{SRE navigation|members|header= Technology team members|description=Miraheze's Technology team is composed of various members who work together to ensure the stability of the infrastructure behind Miraheze. Learn more on Miraheze Meta.|keywords=miraheze tech, miraheze system administrators, miraheze sysadmins}} }}` + + `{{ {{Tech navigation|members|header= Technology team members|description=Miraheze's Technology team is composed of various members who work together to ensure the stability of the infrastructure behind Miraheze. Learn more on Miraheze Meta.|keywords=miraheze tech, miraheze system administrators, miraheze sysadmins}} }}` + **Technology team members**, formerly known as Site Reliability Engineering, are responsible for the technical operation and stability of the infrastructure behind Miraheze. Team members are often referred to as **system administrators** (or **sysadmins**). The team includes volunteers in technical and less-technical roles, including project management and community liaising. You can contact the team at tech `{{ {{@}} }}`miraheze.org. @@ -22,6 +24,8 @@ The team includes volunteers in technical and less-technical roles, including pr ! Grafana (Admin) |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}` +### Chart `{{ {{:Tech:Volunteers/Chart}} }}` + ## See also * [Tech:Organization](/tech-docs/techorganization) * [Board of Directors](https://meta.miraheze.org/wiki/Board_of_Directors) @@ -30,7 +34,7 @@ The team includes volunteers in technical and less-technical roles, including pr * [Category:Documentation](https://meta.miraheze.org/wiki/Category:Documentation) * [Category:Global user groups](https://meta.miraheze.org/wiki/Category:Global_user_groups) -* [Category:System administrators](https://meta.miraheze.org/wiki/Category:System_administrators) +* [Category:Technology team members](https://meta.miraheze.org/wiki/Category:Technology_team_members) ---- **[Go to Source →](https://meta.miraheze.org/wiki/Tech:Volunteers)** \ No newline at end of file