Skip to content

Commit

Permalink
Auto-update Tech namespace pages 2024-09-16 09:02:06.988346
Browse files Browse the repository at this point in the history
  • Loading branch information
Universal-Omega committed Sep 16, 2024
1 parent 56c3dcb commit 3d31683
Show file tree
Hide file tree
Showing 42 changed files with 169 additions and 169 deletions.
6 changes: 3 additions & 3 deletions content/tech-docs/Tech:Data_Processing_Inventory.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@ At the [Board meeting of October 23, 2020](https://meta.miraheze.org/wiki/Board/

| Data type | Subjects | Legal basis | Retention date | Processors |
| --- | --- | --- | --- | --- |
| IP address | Editors, readers | Anonymous editors: consent<br />CheckUser (registered editor): legitimate interests | Anonymous editing: indefinite (attribution mandatory by licensing)<br />CheckUser (registered editor): up to 90 days | DigitalOcean, OVH, RamNode |
| Usernames | Registered editors | Consent (account may not be required<sub>(*reference:* Communities may require registration prior to reading and editing, but Miraheze Limited commits to information access without prior registration.)</sub>) | Indefinite (until account has been renamed or deleted by user or per GDPR request<sub>(*reference:* Due to attribution requirements by licensing, user accounts will not be erased, but accounts will be renamed to apply [pseudonymisation](https://en.wikipedia.org/wiki/Pseudonymization).)</sub>) | DigitalOcean, OVH, RamNode |
| IP address | Editors, readers | Anonymous editors: consent <br />CheckUser (registered editor): legitimate interests | Anonymous editing: indefinite (attribution mandatory by licensing) <br />CheckUser (registered editor): up to 90 days | DigitalOcean, OVH, RamNode |
| Usernames | Registered editors | Consent (account may not be required <sub>(*reference:* Communities may require registration prior to reading and editing, but Miraheze Limited commits to information access without prior registration.)</sub>) | Indefinite (until account has been renamed or deleted by user or per GDPR request <sub>(*reference:* Due to attribution requirements by licensing, user accounts will not be erased, but accounts will be renamed to apply [pseudonymisation](https://en.wikipedia.org/wiki/Pseudonymization).)</sub>) | DigitalOcean, OVH, RamNode |
| Password | Registered users | Legitimate interests (account security) | Indefinite (until changed or removed by user or per GDPR request) | DigitalOcean, OVH, RamNode |
| Email address | Registered users | Consent (not required upon registration), legitimate interests (account security / password reset) | Indefinite (until removed or changed by user or per GDPR request) | DigitalOcean, OVH, RamNode |
| Optional user information (e.g. a user page, real name) | Editors | Consent | Indefinite (until edited or removed by user or per GDPR request) | DigitalOcean, OVH, RamNode |
Expand All @@ -34,7 +34,7 @@ At the [Board meeting of October 23, 2020](https://meta.miraheze.org/wiki/Board/

* Anonymous: user without an account
* Registered: user with an account
* Editors: anonymous or registered users, editing wiki content<sub>(*reference:* All editors are readers, but not all readers are editors.)</sub>
* Editors: anonymous or registered users, editing wiki content <sub>(*reference:* All editors are readers, but not all readers are editors.)</sub>
* Readers: anonymous or registered users, reading wiki content


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ title: Tech:Deleting and moving batches of pages on a wiki
To delete or move large batches of pages on a wiki, execute the following commands for the `deleteBatch.php` and `moveBatch.php` [MediaWiki](https://meta.miraheze.org/wiki/MediaWiki) maintenance scripts in the following sequence:

* Login to `mwtask181` (active maintenance server).
* Upload a text file, named as *subdomain.txt* , ideally, to your shell folder, which contains the list of pages for deletion or moving (include the namespace, where applicable!), replacing the *italicized* portions as applicable.
* Run `sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki=wikidbname -u "Miraheze maintenance script" -r "[[phab:T###|Requested]]" /home/yourshellusername/wikisubdomain.txt`, replacing the ***bolded and italicized*** portions as applicable. **Note:***`deleteBatch.php`* is interchangeable with *`moveBatch.php`* as applicable.
* sudo `sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki=wikidbname -u "Miraheze maintenance script" -r "[[phab:T###|Requested]]" /home/yourshellusername/wikisubdomain.txt`, replacing the ***bolded italicized*** portions as applicable. **Note:***`deleteBatch.php`* is interchangeable with *`moveBatch.php`* as applicable.
* Upload a text file, named as *subdomain.txt*, ideally, to your shell folder, which contains the list of pages for deletion or moving (include the namespace, where applicable!), replacing the *italicized* portions as applicable.
* Run `sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki=wikidbname -u "Miraheze maintenance script" -r "[[phab:T###|Requested]]" /home/yourshellusername/wikisubdomain.txt`, replacing the ***bolded and italicized*** portions as applicable. **Note:** *`deleteBatch.php`* is interchangeable with *`moveBatch.php`* as applicable.
* sudo `sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki=wikidbname -u "Miraheze maintenance script" -r "[[phab:T###|Requested]]" /home/yourshellusername/wikisubdomain.txt`, replacing the ***bolded italicized*** portions as applicable. **Note:** *`deleteBatch.php`* is interchangeable with *`moveBatch.php`* as applicable.
* Logout (if you are done with your business on `mwtask181`).

[Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
Expand Down
4 changes: 2 additions & 2 deletions content/tech-docs/Tech:GitHub.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,8 @@ 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<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) or manually)</sub>
* **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) or manually)</sub>

### ManageWiki

Expand Down
8 changes: 4 additions & 4 deletions content/tech-docs/Tech:MariaDB.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Tech:MariaDB
---

MariaDB<sub>(*reference:* English Wikipedia article: [MariaDB](https://meta.miraheze.org/wiki/w:MariaDB))</sub> is the chosen database software used in production. Currently we run 10.11.x on database servers.
MariaDB <sub>(*reference:* English Wikipedia article: [MariaDB](https://meta.miraheze.org/wiki/w:MariaDB))</sub> is the chosen database software used in production. Currently we run 10.11.x on database servers.

## Configuration

Expand Down Expand Up @@ -33,7 +33,7 @@ An alternative (might be faster in some situations):
```
(the directory at the destination **must** be created before, please specify the correct date as well)

At the destination, the backup must be *prepared* , since the data is not consistent yet. You can do this using mariabackup:
At the destination, the backup must be *prepared*, since the data is not consistent yet. You can do this using mariabackup:
```
[again, raise the soft open files limit] ulimit -Sn 1000000
mariabackup --prepare --open-files-limit=900000 --target-dir=/home/dbcopy/backup-db12-10january2020 --use-memory=2G
Expand Down Expand Up @@ -75,11 +75,11 @@ To revoke grants do the following:
* Run `SELECT User,Host FROM mysql.user;`
* Run `SHOW GRANTS FOR <User_column>@<Host_column>;`
* Run `REVOKE <Text_after_`GRANT`_and_before_ON> on <Table> from <User_column>@<Host_column>;`
**Example:**`REVOKE SELECT, PROCESS, REPLICATION CLIENT on *.* from exporter@81.4.127.174;`
**Example:** `REVOKE SELECT, PROCESS, REPLICATION CLIENT on *.* from exporter@81.4.127.174;`

To drop a user:
* Run `drop user <User_column>@<Host_column>;`
**Example:**`drop user exporter@81.4.127.174;`
**Example:** `drop user exporter@81.4.127.174;`

## Restoring Database from a backup

Expand Down
8 changes: 4 additions & 4 deletions content/tech-docs/Tech:MediaWiki-Compatibility-hi.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ title: Tech:MediaWiki/Compatibility/hi
`{{ {{MediaWiki navigation|compatibility|header=MediaWiki compatibility|description=Miraheze supports a variety of browsers which meet the latest web standards. Their support is fully dependent on upstream support by MediaWiki. Learn more on Miraheze Meta.|keywords=miraheze mediawiki compatibility}} }}` `{{ {{Shortcut|Old}} }}`
Miraheze उन सभी ब्राउज़रों को समर्थित करता है जो मीडियाविकि के उस संस्करण द्वारा समर्थित है जिसपर Miraheze वर्तमान में चल रहा है (इस समय मीडियाविकि `{{ {{CURRENTVERSION}} }}`)।

Miraheze ब्राउज़रों को तीन श्रेणियों में बाँटता है: '**क' वर्ग** (आधुनिक ब्राउज़र, पूर्ण समर्थन), '**ख' वर्ग** (बुनियादी समर्थन), और '**ग' वर्ग** (अनजान):
Miraheze ब्राउज़रों को तीन श्रेणियों में बाँटता है: ' **क' वर्ग** (आधुनिक ब्राउज़र, पूर्ण समर्थन), ' **ख' वर्ग** (बुनियादी समर्थन), और ' **ग' वर्ग** (अनजान):

* '**क' वर्ग** के ब्राउज़रों को मीडियाविकि पूरी तरह से समर्थित करता है और परीक्षण से साबित हुआ है कि वे मीडियाविकि के सभी मूल सुविधाओं को समर्थित करते हैं।
* '**ख' वर्ग** के ब्राउज़रों पर कुछ वेब मानक समर्थित नहीं हैं जैसे पुराने ब्राउज़र। मीडियाविकि कुछ सुविधाओं को अक्षम कर देती है ताकि सामग्री को ठीक से प्रदर्शित किया जा सकते मगर उनके पास फिर भी पूर्ण समर्थन नहीं है।
* '**ग' वर्ग** के ब्राउज़र वे ब्राउज़र हैं जिनके पास अब समर्थन नहीं है या फिर जिनके उपयोगकर्ताओं की संख्या समर्थन के लिए काफी ज़्यादा कम है। 'ग' वर्ग के ब्राउज़र वे ब्राउज़र हैं जिन्हें 'क' वर्ग के ब्राउज़रों की तरह देखा जाता है यानी कि 'ख' वर्ग के ब्राउज़रों की तरह इनके लिए मीडियाविकि सुविधाओं को अक्षम नहीं करता। ऐसा इसलिए किया गया है ताकि बिना बड़े उपयोगकर्ता-समूह के ब्राउज़रों के उपयोगकर्ताएँ मीडियाविकि का पूरा इस्तेमाल कर पाए।
* ' **क' वर्ग** के ब्राउज़रों को मीडियाविकि पूरी तरह से समर्थित करता है और परीक्षण से साबित हुआ है कि वे मीडियाविकि के सभी मूल सुविधाओं को समर्थित करते हैं।
* ' **ख' वर्ग** के ब्राउज़रों पर कुछ वेब मानक समर्थित नहीं हैं जैसे पुराने ब्राउज़र। मीडियाविकि कुछ सुविधाओं को अक्षम कर देती है ताकि सामग्री को ठीक से प्रदर्शित किया जा सकते मगर उनके पास फिर भी पूर्ण समर्थन नहीं है।
* ' **ग' वर्ग** के ब्राउज़र वे ब्राउज़र हैं जिनके पास अब समर्थन नहीं है या फिर जिनके उपयोगकर्ताओं की संख्या समर्थन के लिए काफी ज़्यादा कम है। 'ग' वर्ग के ब्राउज़र वे ब्राउज़र हैं जिन्हें 'क' वर्ग के ब्राउज़रों की तरह देखा जाता है यानी कि 'ख' वर्ग के ब्राउज़रों की तरह इनके लिए मीडियाविकि सुविधाओं को अक्षम नहीं करता। ऐसा इसलिए किया गया है ताकि बिना बड़े उपयोगकर्ता-समूह के ब्राउज़रों के उपयोगकर्ताएँ मीडियाविकि का पूरा इस्तेमाल कर पाए।

नीचे [MediaWiki.org](https://meta.miraheze.org/wiki/mw:) से एक टेबल है जिसमें लिखा है कि कौन-से ब्राउज़र किस श्रेणी में हैं। `{{ {{mw:Compatibility browser}} }}`

Expand Down
2 changes: 1 addition & 1 deletion content/tech-docs/Tech:Nginx.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Adding a new site to NGINX is relatively easy but also depends on what you want

### New Site

To add a new site, you add a .conf file in `/etc/nginx/sites-available/<name>.conf` and then symlink `/etc/nginx/sites-enabled/<name>.conf to``/etc/nginx/sites-available/<name>.conf`
To add a new site, you add a .conf file in `/etc/nginx/sites-available/<name>.conf` and then symlink `/etc/nginx/sites-enabled/<name>.conf to` `/etc/nginx/sites-available/<name>.conf`

With the contents:

Expand Down
Loading

0 comments on commit 3d31683

Please sign in to comment.