Bitnami MediaWiki for Huawei Enterprise Cloud

Transcription

1 Bitnami MediaWiki for Huawei Enterprise Cloud Description MediaWiki is a wiki package originally written for Wikipedia. MediaWiki is an extremely powerful, scalable software and a feature-rich wiki implementation. First steps with the Bitnami MediaWiki Stack Welcome to your new Bitnami application running on Huawei Enterprise Cloud! Here are a few questions (and answers!) you might need when first starting with your application. What is the administrator username set for me to log in to the application for the first time? Username: user What is the administrator password? To obtain the administrator password, click the "Remote Login" menu option next to the server name in the Huawei Cloud Server Console. This will launch a new browser window with an encrypted login session. The application password will be displayed on the login welcome screen. What SSH username should I use for secure shell access to my application? SSH username: root How to connect to the MySQL database? You can connect to the MySQL database from the same computer where it is installed with the mysql client tool. mysql -u root -p

2 You will be prompted to enter the root user password. This is the same as the application password. Find out how to obtain application credentials. How to debug errors in your database? The main log file is created at /opt/bitnami/mysql/data/mysqld.log on the MySQL database server host. How to start or stop the services? Each Bitnami stack includes a control script that lets you easily stop, start and restart services. The script is located at /opt/bitnami/ctlscript.sh. Call it without any service name arguments to start all services: sudo /opt/bitnami/ctlscript.sh start Or use it to restart a single service, such as Apache only, by passing the service name as argument: sudo /opt/bitnami/ctlscript.sh restart apache Use this script to stop all services: sudo /opt/bitnami/ctlscript.sh stop Restart the services by running the script without any arguments: sudo /opt/bitnami/ctlscript.sh restart Obtain a list of available services and operations by running the script without any arguments: sudo /opt/bitnami/ctlscript.sh How to create a full backup of MediaWiki? Backup

3 The Bitnami MediaWiki Stack is self-contained and the simplest option for performing a backup is to copy or compress the Bitnami stack installation directory. To do so in a safe manner, you will need to stop all servers, so this method may not be appropriate if you have people accessing the application continuously. Follow these steps: Change to the directory in which you wish to save your backup: cd /your/directory Stop all servers: sudo /opt/bitnami/ctlscript.sh stop Create a compressed file with the stack contents: sudo tar -pczvf application-backup.tar.gz /opt/bitnami Restart all servers: sudo /opt/bitnami/ctlscript.sh start You should now download or transfer the application-backup.tar.gz file to a safe location. Restore Follow these steps: Change to the directory containing your backup: cd /your/directory Stop all servers: sudo /opt/bitnami/ctlscript.sh stop Move the current stack to a different location: sudo mv /opt/bitnami /tmp/bitnami-backup Uncompress the backup file to the original directoryv

4 sudo tar -pxzvf application-backup.tar.gz -C / Start all servers: sudo /opt/bitnami/ctlscript.sh start If you want to create only a database backup, refer to these instructions for MySQL and PostgreSQL. How to configure outbound settings? Follow these steps: Install two PEAR packages: Mail and Net_SMTP. Go to the console and run the following command. sudo pear install mail sudo pear install net_smtp Add the following code to the end of the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file according to your SMTP server settings. This example shows how to configure it using a Gmail account. Replace USERNAME and PASSWORD with your Gmail account username and password respectively. $wgsmtp = array( 'host' => 'ssl://smtp.gmail.com', 'IDHost' => 'gmail.com', 'port' => 465, 'username' => 'USERNAME@gmail.com', 'password' => 'PASSWORD', 'auth' => true ); Restart the servers. To configure the application to use other third-party SMTP services for outgoing , such as SendGrid or Mandrill, refer to the FAQ.

5 Troubleshooting Gmail SMTP issues If you are using Gmail as the outbound server and you are not able to send correctly, Google may be blocking sign-in attempts from your apps or devices. Depending on whether or not you use Google Apps, the steps to correct this will differ. For Google Apps users If you are a Google Apps user, you will need your administrator to allow users to change the policy for less secure apps. If you are a Google Apps administrator, follow these steps: Browse to the Google Apps administration panel. Click on "Security" and then "Basic settings". Look for the section "Less secure apps" and then click on "Go to settings for less secure apps". Select "Allow users to manage their access to less secure apps". For other Google users If you do not use Google Apps, follow the steps in the following sections, depending on whether 2-step verification has been enabled on the account or not. If 2-step verification has not been enabled on the account, follow these steps: Browse to the "Less secure apps" page and log in using the account you are having problems with. This option is typically required by many popular clients, such as Outlook and Thunderbird, and should not be considered unsafe. Select the "Turn on" option. If 2-step verification has been enabled on the account, you have to generate an app password. Follow these steps: Browse to the "App passwords" page. Click "Select app" and choose the app you're using.

6 Click "Select device" and choose the device you're using. Click the "Generate" button. Enter the app password on your device. Click the "Done" button. Here are other options you may try: Browse to the web version of Gmail and sign in to your account. Once you're signed in, try to enable access for the application again. Browse to the "Unlock Captcha" function page and sign in with your Gmail username and password. Disable IMAP from the Gmail web server interface and enable it again. How to upload files to the server with SFTP? Although you can use any SFTP/SCP client to transfer files to your server, the link below explains how to configure FileZilla (Windows, Linux and Mac OS X), WinSCP (Windows) and Cyberduck (Mac OS X). It is required to use your server's private SSH key to configure the SFTP client properly. Choose your preferred application and follow the steps in the link below to connect to the server through SFTP. How to upload files to the server How to enable HTTPS support with SSL certificates? NOTE: The steps below assume that you are using a custom domain name and that you have already configured the custom domain name to point to your cloud server. Bitnami images come with SSL support already pre-configured and with a dummy certificate in place. Although this dummy certificate is fine for testing and development purposes, you will usually want to use a valid SSL certificate for production use. You can either generate this on your own (explained here) or you can purchase one from a commercial certificate authority.

7 Once you obtain the certificate and certificate key files, you will need to update your server to use them. Follow these steps to activate SSL support: Use the table below to identify the correct locations for your certificate and configuration files. Variable Value Current application URL Example: or Apache /opt/bitnami/apache2/conf/bitnami/bitnami.conf configuration file Certificate file /opt/bitnami/apache2/conf/server.crt Certificate key file /opt/bitnami/apache2/conf/server.key CA certificate bundle file (if /opt/bitnami/apache2/conf/server-ca.crt present) Copy your SSL certificate and certificate key file to the specified locations. NOTE: If you use different names for your certificate and key files, you should reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the corresponding Apache configuration file to reflect the correct file names. If your certificate authority has also provided you with a PEM-encoded Certificate Authority (CA) bundle, you must copy it to the correct location in the previous table. Then, modify the Apache configuration file to include the following line below the SSLCertificateKeyFile directive. Choose the correct directive based on your scenario and Apache version: Variable Apache configuration file Directive to include (Apache v2.4.8+) Directive to include (Apache < v2.4.8) Value /opt/bitnami/apache2/conf/bitnami/bitnami.conf SSLCACertificateFile "/opt/bitnami/apache2/conf/server-ca.crt" SSLCertificateChainFile "/opt/bitnami/apache2/conf/server-ca.crt" NOTE: If you use a different name for your CA certificate bundle, you should reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in the corresponding Apache configuration file to reflect the correct file name. Once you have copied all the server certificate files, you may make them readable by the root user only with the following commands:

8 sudo chown root:root /opt/bitnami/apache2/conf/server* sudo chmod 600 /opt/bitnami/apache2/conf/server* Open port 443 in the server firewall. Refer to the FAQ for more information. Restart the Apache server. You should now be able to access your application using an HTTPS URL. How to create an SSL certificate? You can create your own SSL certificate with the OpenSSL binary. A certificate request can then be sent to a certificate authority (CA) to get it signed into a certificate, or if you have your own certificate authority, you may sign it yourself, or you can use a self-signed certificate (because you just want a test certificate or because you are setting up your own CA). Create your private key (if you haven't created it already): sudo openssl genrsa -out /opt/bitnami/apache2/conf/server.key 2048 Create a certificate: sudo openssl req -new -key /opt/bitnami/apache2/conf/server.key -o ut /opt/bitnami/apache2/conf/cert.csr IMPORTANT: Enter the server domain name when the above command asks for the "Common Name". Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you. Until the certificate is received, create a temporary self-signed certificate: sudo openssl x509 -in /opt/bitnami/apache2/conf/cert.csr -out /opt /bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apach e2/conf/server.key -days 365 Back up your private key in a safe location after generating a password-protected version as follows:

9 sudo openssl rsa -des3 -in /opt/bitnami/apache2/conf/server.key -o ut privkey.pem Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows: sudo openssl rsa -in privkey.pem -out /opt/bitnami/apache2/conf/se rver.key Find more information about certificates at How to force HTTPS redirection? Add the following to the top of the /opt/bitnami/apps/mediawiki/conf/httpd-prefix.conf file: RewriteEngine On RewriteCond %{HTTPS}!=on RewriteRule ^/(.*) [R,L] After modifying the Apache configuration files, restart Apache to apply the changes. How to debug Apache errors? Once Apache starts, it will create two log files at /opt/bitnami/apache2/logs/access_log and /opt/bitnami/apache2/logs/error_log respectively. The access_log file is used to track client requests. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time. The error_log file is used to record important events. This file includes error messages, startup messages, and any other significant events in the life cycle of the server. This is the first place to look when you run into a problem when using Apache.

10 If no error is found, you will see a message similar to: Syntax OK How to modify PHP settings? The PHP configuration file allows you to configure the modules enabled, the settings or the size of the upload files. It is located at /opt/bitnami/php/etc/php.ini. After modifying the PHP configuration file, restart both Apache and PHP-FPM for the changes to take effect: sudo /opt/bitnami/ctlscript.sh restart apache sudo /opt/bitnami/ctlscript.sh restart php-fpm For example, to modify the default upload limit for PHP, update the PHP configuration file following these instructions. How to modify the allowed limit for uploaded files? Modify the following options in the /opt/bitnami/php/etc/php.ini file to increase the allowed size for uploads: ; Maximum size of POST data that PHP will accept. post_max_size = 16M ; Maximum allowed size for uploaded files. upload_max_filesize = 16M Restart PHP-FPM and Apache for the changes to take effect. sudo /opt/bitnami/ctlscript.sh restart apache sudo /opt/bitnami/ctlscript.sh restart php-fpm How to access phpmyadmin?

11 For security reasons, phpmyadmin is accessible only when using as the hostname. To access it from a remote system, you must create an SSH tunnel that routes requests to the Apache Web server from This implies that you must be able to connect to your server over SSH in order to access these applications remotely. IMPORTANT: Before following the steps below, ensure that your Apache and MySQL servers are running. NOTE: The steps below suggest using port 8888 for the SSH tunnel. If this port is already in use by another application on your local machine, replace it with any other port number greater than 1024 and modify the steps below accordingly. Similarly, if you have enabled Varnish, your stack's Apache Web server might be running on port 81. In this case, modify the steps below to use port 81 instead of port 80 for the tunnel endpoint. Windows To access the application using your Web browser, create an SSH tunnel, as described below. Download PuTTY and make sure you can log in to the server console with it following the instructions in the FAQ. Once you have confirmed you are able to log in successfully, log back out. Reconnect to the server using PuTTY, this time adapting the steps to include an additional SSH tunnel. When configuring the new SSH session in PuTTY, additionally navigate to the "Connection -> SSH -> Tunnels" section and create a secure tunnel by forwarding port 80 on the server to port 8888 on the local host ( or localhost). Click the "Add" button to add the secure tunnel configuration to the session. Here is an example:

12 Go back to the "Session" section and save your changes by clicking the "Save" button. Click the "Open" button to open an SSH session to the server. The SSH session will now include a secure SSH tunnel between the two specified ports. While the tunnel is active, you should be able to access the phpmyadmin console through the secure SSH tunnel you created, by browsing to To log in, use username root for MySQL and the application password from the detail page for your cloud server. If you are unable to access phpmyadmin, verify that the SSH tunnel was created by checking the PuTTY event log (accessible via the "Event Log" menu):

13 Linux and Mac OS X To access the application using your Web browser, create an SSH tunnel, as described below. Open a new terminal window on your local system (for example, using "Finder -> Applications -> Utilities -> Terminal" in Mac OS X or the Dash in Ubuntu). Make sure you can log in to the server console following the instructions in the FAQ. Once you have confirmed you are able to log in successfully, log back out. Run the following command to configure the SSH tunnel. Remember to replace SERVER-IP with the public IP address or hostname of your server. Enter your SSH password when prompted. ssh -N -L 8888: :80 bitnami@server-ip If you are using a private key to connect to the server, use the following command instead, remembering to replace KEYFILE with the path to your private key and SERVER-IP with the public IP address or hostname of your server: ssh -N -L 8888: :80 -i KEYFILE bitnami@server-ip NOTE: If successful, the above commands will create an SSH tunnel but will not display any output on the server console. While the tunnel is active, you should be able to access the phpmyadmin console through the secure SSH tunnel you created, by browsing to To log in, use username root for MySQL and the application password from the detail page for your cloud server.

14 How to install Collection extension on MediaWiki? The Collection extension allows you to organize personal selections of pages in a collection. To do it, the extension uses a public render server where the jobs are sent and processed. Please keep in mind that if your Mediawiki installation is not public (it is a local installation or it can't be accessed from the Internet), you will need to install your own Render Server. The Collection developers have some suggestions about it here. To install the Collection plugin, please follow the steps below: Download the latest Collection version from the official Mediawiki extension page. Uncompress the downloaded file in the Mediawiki extensions directory. The command below should create the Collection directory in the Mediawiki extensions directory: tar -xzf Collection-*.tar.gz -C /opt/bitnami/apps/mediawiki/htdocs /extensions Add the Collection plugin to the Mediawiki LocalSettings.php file: echo 'require_once "$IP/extensions/Collection/Collection.php";' >> /opt/bitnami/apps/mediawiki/htdocs/localsettings.php Once you have completed all the steps above, you should see new options in the MediaWiki menu:

15 If you already have your own Renderserver, remember to add the URL in /opt/bitnami/apps/mediawiki/htdocs/localsettings.php, as below: $wgcollectionmwserveurl = " How to install Math extension on MediaWiki? If you want to install the Math extension on MediaWiki, please follow these steps: Go to the MediaWiki extensions directory: cd /opt/bitnami/apps/mediawiki/htdocs/extensions Download the extension from wget tar.gz Extract the code: tar -xzf Math-REL1_ tar.gz Edit the permissions sudo chmod 775 Math/

16 sudo chown -R bitnami:daemon Math/ Edit the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file and add this code at the end of the file require_once ( "$IP/extensions/Math/Math.php" ); Run the update script which will automatically create the necessary database tables that this extension needs. sudo /opt/bitnami/use_mediawiki cd /opt/bitnami/apps/mediawiki/htdocs php maintenance/update.php Check that Math extension is installed by visiting the page Special:Version in your MediaWiki installation. You will see something like the image below: How to install MultimediaViewer extension on MediaWiki? The MultimediaViewer extension gives wiki users a different interface for viewing full-size, or nearly full-size, images in their browser without extraneous page loads or confusing interstitial pages. To install the MultimediaViewer plugin, please follow the steps below: Download the latest MultimediaViewer version from the official Mediawiki extension page. Uncompress the downloaded file in the extensions directory of Mediawiki. The command below should create the Collection directory in the Mediawiki extensions directory: tar -xzf MultimediaViewer-*.tar.gz -C /opt/bitnami/apps/mediawiki/ htdocs/extensions

17 Add the MultimediaViewer plugin to the Mediawiki LocalSettings.php file: require_once "$IP/extensions/MultimediaViewer/MultimediaViewer.p hp"; If you have enabled PageSpeed you will need to disable it for the images directory. To do this, edit the file /opt/bitnami/apps/mediawiki/conf/htaccess.conf and modify the Directory directive for that directory. The Directory directive should look like this: <Directory "/opt/bitnami/apps/mediawiki/htdocs/images"> # Protect against bug <IfModule rewrite_module> RewriteEngine On e] RewriteCond %{QUERY_STRING} \.[^\\/:*?\x22<> %]+(# \? $) [nocas RewriteRule. - [forbidden] </IfModule> ModPagespeed off </Directory> How to install ParserFunctions extension on MediaWiki? If you want to install the ParserFunctions extension on MediaWiki, please follow these steps: Go to the MediaWiki extensions directory: cd /opt/bitnami/apps/mediawiki/htdocs/extensions Create the ParserFunctions directory: mkdir ParserFunctions Change to the new directory:

18 cd ParserFunctions Download the extension from wget -O parserfunctions.zip awiki/extensions/parserfunctions&h=refs/heads/master&format=gz && unzip parserfunctions.zip Edit the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file and add this code at the end of the file: require_once( "$IP/extensions/ParserFunctions/ParserFunctions.ph p" ); If you want to use the integrated string functionality, add just after that line: $wgpfenablestringfunctions = true; Restart the Apache server sudo /opt/bitnami/ctlscript.sh restart apache How to install Parsoid extension on MediaWiki? If you want to install the Parsoid extension on MediaWiki, please follow these steps: Go to the MediaWiki extensions directory: cd /opt/bitnami/apps/mediawiki/htdocs/extensions Download the extension from wget f5500c1.tar.gz Extract the code:

19 tar -xzf Parsoid-REL1_25-f5500c1.tar.gz Edit the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file and add this code at the end of the file wfloadextension( 'Parsoid' ); Restart the Apache server sudo /opt/bitnami/ctlscript.sh restart apache Check that Parsoid extension is installed by visiting page Special:Version in your MediaWiki page. You will see something like this: NOTE: If you are using MediaWiki 1.24 or earlier, you will need to add the line below to your LocalSettings.php file instead. require_once "$IP/extensions/Parsoid/Parsoid.php"; How to install a plugin on MediaWiki? Refer to the other sections in this document for specific plugin information. How to install Semantic Bundle extension? Semantic Bundle (abbreviated as SB) is a pre-packaged bundle of extensions for use with wikis that are based around the Semantic MediaWiki extension. It is a suitable alternative if you cannot run Composer to install or upgrade SMW (1.9+) and a number of other extensions that require Composer, such as Maps (3.0+). Do not run Composer if you want to install Semantic Bundle. Follow these steps: Download the ZIP or TGZ archive and unzip it to /opt/bitnami/apps/mediawiki/htdocs/extensions/. For example, assuming you downloaded the archive in /tmp:

20 cd /opt/bitnami/apps/mediawiki/htdocs/extensions/ unzip /tmp/semanticbundle zip Change to the extension directory and create the configuration file: cd /opt/bitnami/apps/mediawiki/htdocs/extensions/semanticbundle cp SemanticBundleSettings.sample.php SemanticBundleSettings.php Include the SemanticBundleSettings.php and SemanticBundle.php files in the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file: require_once( "$IP/extensions/SemanticBundle/SemanticBundleSetti ngs.php" ); require_once( "$IP/extensions/SemanticBundle/SemanticBundle.php" ); Log in to MediaWiki as an administrator. Navigate to the page at and click the "Initialize or upgrade tables" button. After successful initialization, edit the /opt/bitnami/apps/mediawiki/htdocs/extensions/semanticbundle/seman ticbundlesettings.php file and uncomment the extensions you would like to use. NOTE: It's strongly recommended to initialize Semantic MediaWiki before you include (uncomment) any of the other SemanticBundle extensions, to avoid potential errors from extensions that require Semantic MediaWiki. How to install Semantic MediaWiki extension on MediaWiki with Composer? You can install Semantic MediaWiki using composer. To do so, please run the following commands: cd /opt/bitnami/apps/mediawiki/htdocs php /opt/bitnami/php/bin/composer.phar update php /opt/bitnami/php/bin/composer.phar require mediawiki/semantic-mediawiki "~2.0"

21 php maintenance/update.php If the last command (update.php) wasn't successful, please try updating from the browser following these steps. Finally, enable semantics for your domain, adding this line at the end of your /opt/bitnami/apps/mediawiki/htdocs/localsettings.php. You need to use your own MediaWiki domain instead of example.com: enablesemantics( 'example.com' ); If you get a warning like this: Warning: This development build of composer is over 30 days old. It is re commended to update it by running "/opt/bitnami/php/bin/composer.phar se lf-update" to get the latest version. Execute the suggested command and try the steps again. Refer to this page for more information. How to install VisualEditor extension on MediaWiki? If you want to install the VisualEditor extension on MediaWiki, please follow these steps: Go to the MediaWiki extensions directory: cd /opt/bitnami/apps/mediawiki/htdocs/extensions Create the VisualEditor directory: mkdir VisualEditor Go to the new directory: cd VisualEditor Download the extension from

22 wget -O visualeditor.zip ki/extensions/visualeditor&h=refs/heads/master&format=gz && unzip visualeditor.zip Edit the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file and add this code at the end of the file: require_once("$ip/extensions/visualeditor/visualeditor.php"); // OPTIONAL: Enable VisualEditor in other namespaces // By default, VE is only enabled in NS_MAIN //$wgvisualeditornamespaces[] = NS_PROJECT; // Enable by default for everybody $wgdefaultuseroptions['visualeditor-enable'] = 1; // Don't allow users to disable it $wghiddenprefs[] = 'visualeditor-enable'; // OPTIONAL: Enable VisualEditor's experimental code features //$wgvisualeditorenableexperimentalcode = true; Restart the Apache server: sudo /opt/bitnami/ctlscript.sh restart apache NOTE: You will be able to use VisualEditor to create new Wiki Pages, but not to edit them. If you want to use VisualEditor to edit them, you will need to follow the official Parsoid installation guide. How to upgrade MediaWiki? It is strongly recommended that you create a backup before starting the update process. If you have important data, it is advisable that you create and try to restore a backup to ensure that everything works properly.

23 Migrating the database from an old version to a new one To migrate the database from an old version to a new one, follow these steps: Launch a new MediaWiki cloud server instance. Copy the database backup to the new server. Stop all servers and start only MySQL. sudo /opt/bitnami/ctlscript.sh stop sudo /opt/bitnami/ctlscript.sh start mysql Remove the previous database and create the new one. You can configure the database user password with a secure password. mysql -u root -p Password: **** mysql> drop database bitnami_mediawiki; mysql> create database bitnami_mediawiki; mysql> grant all privileges on bitnami_mediawiki.* to 'bn_mediawi ki'@'localhost' identified by 'DATABASE_PASSWORD'; Restore the new database: mysql -u root -p bitnami_mediawiki < backup.sql Edit the MediWiki configuration file to update the database user password (the same that you set previously) at /opt/bitnami/apps/mediawiki/htdocs/localsettings.php: $wgdbpassword = "DATABASE_PASSWORD"; Copy the /opt/bitnami/apps/mediawiki/htdocs/files directory from the old installation to the new one. If you have installed plugins in the previous version, copy the folders from the vendor/plugins directory into the new installation directory, into the plugins directory. Restart the servers.

24 sudo /opt/bitnami/ctlscript.sh restart How to upgrade the MediaWiki database? You can upgrade the MediaWiki database in two ways: from the command line or from the web browser (since version 1.17). Upgrading from the command line is recommended, since this reduces the risk of the upgrade process being interrupted by a timeout or connection reset. Command-line upgrade Make sure that your web server (such as Apache) and your database sever (such as MySQL) are running. From the command line execute: cd /opt/bitnami/apps/mediawiki/htdocs php maintenance/update.php MediaWiki will inspect the existing schema and update it to work with the new code, adding tables and columns as needed. If you use a shared database, you should pass the doshared parameter if you want the shared tables to be updated. Otherwise they won't be touched by the update script. Web browser upgrade NOTE: If your database is already large in size and in high production usage, then you should not be using the Web updater, as the update process might time out when the script's maximum execution time is reached. In that case you should use the command-line interface (not from the web). Always backup before performing database maintenance. Follow these steps: Navigate your browser to /mw-config/. For example, if your wiki is at mydomain.com/mediawiki/main_page, then navigate to mydomain.com/mediawiki/mw-config/. Select your language and click continue. The existing installation should be detected. Follow the instructions on the screen to upgrade it. If asked for the "upgrade key", open /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file and look for the key assigned to $wgupgradekey. How to optimize MediaWiki?

25 Enable page caching by adding the following entries to the end of the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file: $wgusefilecache = true; /* default: false */ $wgfilecachedirectory = "$IP/cache"; $wgshowipinheader = false; Execute this command to set proper directory permissions: sudo chmod g+w /opt/bitnami/apps/mediawiki/htdocs/cache For more information, refer to these resources: MediaWiki manual pages for caching MediaWiki optimization instructoins How to change the MediaWiki URLs to pretty URLs? NOTE: Pretty links have been included by default in Bitnami MediaWiki for Unix systems since version It is not possible to include them in in Windows systems, due to the colon (:) in the Special pages URL. This is described at The following steps should be performed to convert MediaWiki URLs to pretty URLs: Add the following lines to the /opt/bitnami/apps/mediawiki/conf/httpd-app.conf file, inside the Directory directive <Directory "/opt/bitnami/apps/mediawiki/htdocs">... RewriteEngine On RewriteBase /mediawiki/ RewriteRule ^index\.php$ - [S=1] RewriteCond %{REQUEST_FILENAME}!-f RewriteCond %{REQUEST_FILENAME}!-d RewriteRule. /mediawiki/index.php [L]

26 ... </Directory> Add the following lines at the end of the /opt/bitnami/apps/mediawiki/htdocs/localsettings.php file: $wgarticlepath = "/mediawiki/$1"; $wgusepathinfo = true; Restart the server. All the links will now be "pretty" links.