Manual:Maintenance scripts/hi

The maintenance scripts are used to perform various administrative, import, maintenance, reporting and upgrade tasks. The scripts are written in PHP and live in the  subdirectory of MediaWiki installs.

सामान्य उपयोगिता और गुणवत्ता की बदलती डिग्री के साथ दर्जनों लिपियाँ हैं। उपयोग करने से पहले आपको एक स्क्रिप्ट पर प्रलेखन को ध्यान से पढ़ना चाहिए; यदि कोई स्क्रिप्ट प्रलेखित नहीं है, तो उसे चलाने में अतिरिक्त सावधानी बरतें।

विन्यास The  and   configuration variables must be set in order to run maintenance scripts that need to alter the structure of the database (like ) if the user configured in  doesn't have enough permissions. Alternatively, you can pass the --dbuser and --dbpass parameters to the script. The values for these variables differ based on the database engine that is being used to power your installation of MediaWiki. यदि कॉन्फ़िगर नहीं किया गया है, तो यह में कॉन्फ़िगर किए गए उपयोगकर्ता का उपयोग करेगा।

MySQL
Some of the maintenance scripts require database permissions that, for security reasons, the main MediaWiki database account should not have. A separate database account with 'superuser' privileges for just the MediaWiki database should be created (if it does not already exist.) If the database that you use for MediaWiki is called, then the following SQL would create such a user who can exercise superuser privileges on localhost.:

Once the account exists, the account name should be set in the  configuration variable. Like other configuration variables,  should be set in. A password for  must be set in the   configuration variable.

PostgreSQL
PostgreSQL uses a different security model than MySQL and the same PostgreSQL server account used for day-to-day operation of the MediaWiki installation must also be used for running the maintenance scripts. This is necessary to ensure that the owner for new tables created by the maintenance scripts is set correctly. You don't need to set  or   at all.

लिपियों को चलाना
रखरखाव लिपियों को तब कमांड लाइन से चलाया जाना चाहिए। जो उपयोगकर्ता अपने टर्मिनल से सीधे सर्वर तक नहीं पहुंचते हैं, वे आमतौर पर के माध्यम से एक कनेक्शन स्थापित करेंगे। For Linux/Unix users this is by using the ssh client in a shell. For Windows users, one can use the SSH command line tool introduced in Windows 10 or alternatively use a third-party tool such as PuTTY shown below or use Windows Subsystem for Linux.

Required program for Windows users: PuTTY or any terminal emulator


 * Step 1: Download and run PuTTY, a terminal emulator.
 * Step 2: In PuTTy, under the Host Name (or IP address) enter the IP Address of your web hosting site (Contact your website provider if necessary) and click Open.


 * Step 3: A command screen will pop up. At the login as: line enter the FTP user name.


 * Step 4: Enter the FTP password.


 * Step 5: Change the current directory to the maintenance subdirectory. You can type  to see what folder you are currently in. The maintenance folder is in the root mediawiki folder.


 * चरण 6: रखरखाव स्क्रिप्ट को निष्पादित करें जिसे चलाने की आवश्यकता है:


 * If you get an error (for example: php.exe is no valid Win32 application), try the following:


 * विंडोज में, कमांड है:

मानक कमांड लाइन विकल्प
Almost every PHP script in  supports several standard options:
 * --help
 * मदद संदेश प्रदर्शित करता है


 * --conf &lt;path&gt;
 * Location of LocalSettings.php, if not default (at parent directory of the script)


 * --dbuser &lt;username&gt;
 * स्थानीय खाते में निर्दिष्ट एक के बजाय उपयोग करने के लिए डेटाबेस खाता। एफपी, उन लिपियों के लिए उपयोग नहीं किया जाता है जिनके लिए डेटाबेस कनेक्शन की आवश्यकता नहीं होती है या जब SQLite डेटाबेस बैकेंड का उपयोग किया जाता है


 * --dbpass &lt;password&gt;
 * Database password to use instead of the one specified in LocalSettings.php, not used for scripts that don't require a database connection or when SQLite database backend is used


 * --globals
 * डिबगिंग के लिए प्रसंस्करण के अंत में आउटपुट ग्लोबल्स


 * --memory-limit &lt;value&gt;
 * Set memory limit for the script. Accepts ordinary numbers, standard php.ini abbreviations (1024K, 20M, 1G),  for no limit (will be used by default if omitted) and   for no change.


 * --quiet
 * गैर-त्रुटि आउटपुट को दबाएं


 * --wiki &lt;id&gt;
 * Wiki ID for wiki farms. This may be of the form  or  . LocalSettings.php will be run with the   and   constants defined accordingly.


 * --profiler
 * Profiler output format (usually "text").


 * --mwdebug
 * Enable built-in MediaWiki development settings.

मीडियाविकि उन संस्थापनों का उपयोग करता है, जो सिमिलिंक
ऐसे मामलों में जहां MediaWiki php फाइलें एक केंद्रीय इंस्टॉलेशन से मेल खाती हैं, आपको LocalSettings.php फाइल के पथ के रखरखाव स्क्रिप्ट को निर्दिष्ट करने की आवश्यकता होगी। उदाहरण के लिए

php maintenance/importImages.php --conf /var/wwwdata/website.org/wiki/LocalSettings.php /tmp/wikiimages .jpg .png .svg

अन्यथा आपको यह त्रुटि मिलेगी:

A copy of your installation's LocalSettings.php must exist and be readable in the source directory.

MediaWiki installs that use shared settings (family type)
Sometimes MediaWiki is installed as a family for many languages and settings (LocalSettings.php) are split to common part and language parts (see ) where common part is located outside of /w directory and accessed using relative link. In this case maintenance scripts will not work when running them in /w/maintenance directory. Run them from /w directory instead:

नो शेल एक्सेस
On many shared hosts, you won't have shell access. The following extensions may be useful to run maintenance scripts via the web: and.

रखरखाव लिपियों की सूची
इसके बजाय शायद पुरानी सूची में,


 * https://doc.wikimedia.org/mediawiki-core/master/php/ - इसका उत्पन्न प्रलेखन सारांश देखें। (Files > File List > maintenance in the tabs or left-hand navigation sidebar)
 * https://doc.wikimedia.org/mediawiki-core/master/php/ - इसका उत्पन्न प्रलेखन सारांश देखें। (Files > File List > maintenance in the tabs or left-hand navigation sidebar)

Here is the list of files included in the  subdirectory located at the root of a MediaWiki installation. You can contribute to this manual by keeping this list up to date, adding a description of these files' specific purpose and of how an administrator should use them (command line examples, etc.). Be aware that these were created and named on an ad hoc basis so have some usability issues.

इसे भी देखें

 * maintenance/README
 * maintenance/README
 * maintenance/README
 * maintenance/README
 * maintenance/README