Fusion Core system requirements

Check hosting, PHP, database, permissions, HTTPS, and automation requirements before installing Fusion Core.

Check these requirements before installing Fusion Core or moving an existing DHRU Fusion website to Fusion Core. Your hosting provider can help configure PHP, the database, HTTPS, and scheduled tasks.

Check your server with the PHP checker

Download the Fusion Core requirements checker (ZIP, version 1.0.0).

  1. Download and extract the ZIP on your computer.
  2. Upload fusion-core-check.php to your website's public folder.
  3. Open https://your-domain.example/fusion-core-check.php in your browser, using the same website and PHP version you plan to use for Fusion Core.
  4. Fix the items marked Fix, then select Check again. Use Download report to share the results with your hosting provider.
  5. Delete fusion-core-check.php from the server when you have finished.

The checker runs independently of Fusion Core and does not need ionCube to display its results. It checks PHP, extensions, and PHP settings without collecting credentials, reading application configuration, changing files, or sending results elsewhere.

Database version and permissions, HTTPS certificates, web-server routing, application-folder permissions, outbound connectivity, scheduled jobs, and available disk space still need confirmation. Run the official installer for the complete checks required by your package.

Hosting and website address

Fusion Core runs on your own hosting account. You need a web server that runs PHP, a MySQL or MariaDB database, a public domain or subdomain, and a valid HTTPS certificate.

The hosting account must let you keep the private DhruFusionCore folder outside the website's public document root. The domain must point to the package's public_html folder. Keep both folders beside each other; do not put the private folder inside public_html.

Use the final public HTTPS website address during setup, for example https://shop.example.com. License activation uses the website root, without an extra path, query string, or custom port. Open setup on that same hostname.

Apache must honor the supplied .htaccess rules. Other web servers, including nginx, need equivalent routing and access restrictions configured by your hosting provider.

PHP and required extensions

  • PHP 8.3 or newer, in a version supported by the official package and its ionCube Loader.
  • ionCube Loader 15.0 or newer, compatible with the selected PHP version, for the commercial package.
  • Required extensions: PDO MySQL (pdo_mysql), OpenSSL, OPcache, Intl, BCMath, GD, and Sodium.
  • PHP must support Argon2id password hashing, secure random numbers, and HTTPS URL streams.

Enable these extensions for the website's PHP version. The PHP configuration shown by an SSH command may differ from the configuration used by the website. If you use PHP from a scheduled command, configure that PHP version as well.

The installer also lists recommended extensions: cURL, Mbstring, Fileinfo, and ZIP. Enable them where possible. ZIP is needed for features that open ZIP packages, including automatic updates and the upgrade wizard's downloadable file backup.

PHP settings

Configure these values in the website's PHP settings. In cPanel, these are normally managed through the PHP version/extension controls and MultiPHP INI Editor; names vary by host.

  • memory_limit: at least 128M.
  • max_execution_time: at least 30 seconds. Longer installation or upgrade operations may need a higher limit.
  • max_input_time: at least 60 seconds; PHP's unlimited or inherited setting is also accepted.
  • file_uploads: On.
  • upload_max_filesize: at least 10M.
  • post_max_size: at least 16M, and greater than upload_max_filesize.
  • max_file_uploads: at least 3.
  • allow_url_fopen: On.
  • opcache.enable: On.
  • max_input_vars: at least 1000.
  • The upload temporary directory must exist and be writable by the website's PHP user.

If you increase the upload limit, increase post_max_size enough to allow the upload and form overhead. Web-server, proxy, and PHP-FPM timeouts can also interrupt a long operation even when PHP's own limits pass.

The requirements screen in your downloaded package is the final check. If it requests a higher value, meet that value before continuing.

Database

Use MySQL 8.0 or newer or MariaDB 10.6 or newer. The database account needs permission to read and write data and create or change tables and indexes during installation and upgrades.

For a new website, create a dedicated, empty database and assign a database user to it. Have the host, port, database name, username, and password ready. Use the full database and username, including any prefix added by your hosting account.

For a legacy upgrade, keep the existing Fusion database. Do not point the new-installation form at a live or legacy database. Follow Upgrade legacy DHRU Fusion to Fusion Core.

File permissions and storage

PHP needs write access to the folders listed by setup, including private storage and configuration folders and the public assets/uploads folders. Correct the file owner or permissions for your hosting account; do not make the entire website writable by everyone.

Keep enough free disk space for the package, your customer files, and backups. Updates need additional temporary space for the downloaded package, extracted files, and recovery copies. Storage and memory needs grow with your customer data and workload; the PHP memory setting above is not a server RAM sizing recommendation.

Network access, license, and automation

Have an eligible Fusion Core service in your Dhru account. The website needs outbound HTTPS access for activation, license renewal, updates, and any supplier or payment integrations you use. Your host must allow certificate verification to work and keep the server clock accurate.

Arrange a scheduler that can run the automation jobs at the interval shown in Admin. Fusion Core supports hosting-panel and external scheduling options. Use the commands or URLs generated by your own installation and keep any included token private.

Run the final check

Upload the official package, configure the domain's document root, and open https://your-domain.example/setup/. Fix every failed required check before continuing. A successful requirements check confirms the checked settings; it does not replace a backup or prove that every supplier, payment provider, or scheduled job is working.

Next: Install Fusion Core.