1. VW4
  2. Minimum Requirements
Printable Version

https://www.vaultwiki.org/pages/Help/VaultWiki-4-Manual/VW4:Minimum-Requirements
This page is a chapter in VW4 Installing VaultWiki

This page has been seen 2,663,598 times.

    • Created by on
      Last updated by on
Before installing VaultWiki, you should make sure your server meets the minimum requirements to run VaultWiki. If your server does, you can safely proceed to the next step. Otherwise, you may want to consider contacting your system administrator, upgrading your hosting account, or opting not to use VaultWiki.

PHP

A PHP version of 5.5.0 or higher but lower than 8.2.0 is needed to run VaultWiki. Since versions of PHP below 7.3.0 have reached End-of-Life status by the developers of PHP, a PHP version of 7.4.0 or higher is recommended.

Note:If you are using VaultWiki with vBulletin, keep in mind that only vBulletin versions 4.2.5 and higher are compatible with PHP versions 7.0.0 and higher, and vBulletin versions 4.2.1 and higher are compatible with PHP versions 5.4.x-5.6.x. If you need to use an incompatible version of vBulletin with PHP 5.5.0, make sure to disable the 'display_errors' configuration option in your php.ini file. It is not possible to use vBulletin versions earlier than 4.2.5 with PHP 7.0.0.

php.ini Configuration

If using PHP's Zend Opcache, enabled with opcache.enabled = 1:
  • opcache.fast_shutdown (default: disabled) must not be enabled. It has bugs that affect reliability of the web-server<->PHP connection.
  • If the PHP version is less than 5.5.0:
    • opcache.validate_timestamps (default: enabled) must not be disabled
    • opcache.revalidate_freq must be less than 10.

MySQL

A MySQL version of 4.4.1 or higher is needed to run VaultWiki. Due to performance improvements, a MySQL version of 5.1.0 or higher is recommended.

A MySQL max_allowed_packet configuration setting of 1M or higher is needed to run VaultWiki. For heavy use, at least 2M is recommended.

vBulletin Warning:vBulletin forums that contain at least one modification will need at least 2M max_allowed_packet. Due to a design flaw in vBulletin 3 and 4, the minimum requirement scales with the number of add-ons installed and the number of phrases in your database. For this reason, you may not be able to install any add-ons, including VaultWiki, unless you are able to increase your max_allowed_packet as needed. vBulletin support staff recommends at least 64M when using add-ons.

Disk Space

VaultWiki uses about 12 MB of storage space on disk just to host its core files. At least 1 GB of additional space is recommended for the database storage that will be accrued as your wiki sees use. Another minimum 1 GB of additional space is recommended so that users can upload attachments.

Forum Software

VaultWiki requires an existing forum installation. Supported forum softwares include:
  • vBulletin versions 3.6.0 - 3.8.8, 4.0.0 - 4.1.12, 4.2.1 - 4.2.5
  • XenForo versions 1.2.0 - 2.2.15

Memory

On its own during normal use, VaultWiki can use up to 8 MB of system memory in order to function properly. However, in most usage scenarios, VaultWiki will be working together with forum software, so total memory consumption will typically be higher. To support this, a minimum of 32 MB of system memory is required. For heavy use or other high load applications, a minimum of 128 MB is recommended.

Shared Hosts and Other Limitations

Some hosting providers, particularly shared hosts, put a cap on the number of inodes (usually, files and folders) or database tables customers can have in their hosting accounts. Some examples are caps of 100,000 inodes, 1,000 database tables, or 1 GB per database. You should check the terms of your hosting contract or contact your server administrator if you are unsure if such a limit applies to you or what that limit may be.

VaultWiki contains a significant number of files and will use about 5,000 inodes towards your limit for just its core files. VaultWiki will also add about 75 tables to your database.