Check the release requirements, the theme/plugin combination and the directories that need controlled write access. A database export is not a backup of a Grav website's content.

Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.

1. Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
2. Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
3. Find Grav and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
4. Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. For this flat-file CMS, review the file-backup and update choices. Do not expect a database export to contain the site content.
5. Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.

Install the intended current package, configure the site identity and URLs, and set up administrative access only where the chosen package includes it. Review caching and any scheduled maintenance required by enabled plugins.

For a Grav site, a useful recovery test restores a copy of the actual files into an isolated location. Include the site's content, uploaded media, configuration, installed themes and plugin data required by your chosen release. Preserve hidden files and the supported web-server rules.

1. Select a recently published page with an image and a customized theme setting.
2. Restore the matching file backup into the test location and adjust only the copy's environment settings.
3. Check that the page, image and setting all reappear, and verify any administrative access separately.

A database export from the hosting account does not recover Grav's flat-file content. A page that renders from cached output also does not prove that the editable source files have been recovered.

Publish a sample page, upload a file and check a clean guest response. Inspect a backup to confirm content, configuration, themes and plugin settings are included.

After deployment, stale cached output can conceal a correct content change. Use the supported cache-clear operation, then inspect configuration and file ownership if the problem continues.

Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.

• Choosing and managing applications with Softaculous
• Opening Softaculous and finding your installations in cPanel
• Changing PHP versions, extensions and application limits
• Creating Web Hosting backups and planning a restore
• Installing WebsiteBaker and checking the first setup

• Softaculous installation workflow
• Softaculous cms catalogue