They require SQLite with FTS3 module compiled-in, which is usually present in most modern builds. Search capabilities for SQLite backend was introduced in MediaWiki 1.16. If you enter nothing into the "SQLite data directory" field, your $wgSQLiteDataDir will be left empty, which corresponds to data directory in the parent of the document root, however this directory might be different for web scripts and maintenance scripts run from command line, so specifying it explicitly is recommended.If SQLite module for PHP is properly installed, MediaWiki installer ( /mw-config/index.php) should offer you an option to use SQLite.Or, if you feel like it, you could put it in the web root somewhere and make sure to use webserver config to deny access to it. Anything outside of the webroot should be safe it's good to keep it nearby. Where should you put the SQLite database itself? The default path seems to be $IP/./data/$dbname.sqlite.You should uncomment the following line in your php.ini The PHP PDO SQLite module needs to be loaded.To install SQLite3 on a Debian or Ubuntu based system, use apt install php-sqlite3.Several extensions are known to have database update or installation issues with SQLite: AbuseFilter, Echo, Flow, and LiquidThreads.Īt least SQLite version 3.8.0+ is required.Īlso, in order to use full text search, SQLite must be compiled with FTS3 module enabled (most builds have it out of the box these days).Although SQLite has its own search engine, it's not supported by more advanced solutions such as Lucene.SQLite is not that scalable, so if you have a large and popular wiki, you should use MySQL.The entire database is stored as a single cross-platform file, simplifying backups and migration. You are not restricted by artificial database limitations on shared hosts.The former also means that SQLite is much more suitable for portable MediaWiki installs running from a USB stick.You don't have to install and maintain a standalone database server such as MySQL this significantly reduces efforts spent on administration and removes some points of failure.Using SQLite as database backend for MediaWiki has its own pros and cons: MediaWiki uses SQLite's functionality through simple function calls, which reduces latency in database access as function calls are more efficient than inter-process communication. Unlike client-server database management systems, the SQLite library is linked into PHP and thus becomes an integral part of the server process. SQLite is an open-source database library released into public domain. The decision to use SQLite, MySQL, or another database system should ideally be made before you create your wiki, as it is difficult to convert from a SQLite database to a MySQL database once you have started using your wiki. In case your wiki may grow to have many concurrent users and a large amount of content, it would be better to use a database system that supports the primary-replica model such as MySQL.Īs a result, if your wiki may depend on using these extensions, or it may need to use a primary-replica database system, it is best to use a MySQL database for your wiki. Second, SQLite does not scale beyond one server. There are two important caveats to using SQLite for MediaWiki.įirst, while many extensions do support SQLite, there are some popular extensions that still do not support it to this day. Support for SQLite by extensions which make database changes is varied. MediaWiki requires SQLite 3.8.0 or later. The database most commonly used with MediaWiki is MySQL. MediaWiki supports SQLite since 1.17, but please note that this is second-class support, and you may likely run into some bugs. The purpose of this page is to collect information and experiences about running MediaWiki on SQLite.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |