Identify the Bolt major version you intend to run and follow documentation for that exact branch. A catalogue package for an older major release should not be treated as the current vendor installation method.

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. Identify the Bolt major version and supported PHP/extensions before choosing a package. Back up an existing site and prepare a separate project directory.
2. Use the official Composer project installation for the selected release. Follow its local development instructions in an isolated environment first.
3. Choose the intended database backend and store connection settings privately. Do not replace an existing database with sample content.
4. Review the documented setup process, including schema initialization and administrator creation. Apply it only to the intended new database or a tested migration copy.
5. For hosting, configure the domain document root to the project's public directory. Keep source configuration and private data outside public download access.
6. Deploy the reviewed project with compatible dependencies and production settings, then test content editing, routes and uploaded media.

For example, a project at /home/ACCOUNT/sites/example uses /home/ACCOUNT/sites/example/public as its public document root. The temporary development server shown in a local quick start does not replace a production web-server configuration. Check the documentation for your exact Bolt branch before using setup commands.

Check the required PHP, database and dependency tools. Use the publisher's current installation workflow when needed, configure the intended public root, and create content types and editor accounts deliberately.

Create and publish a test entry, verify its route and template, and test media upload with a limited editor. Confirm development diagnostics are disabled on the public site.

Major-version changes can alter templates, configuration and storage. Build an isolated migration copy and verify field mappings and content exports before replacing an older Bolt installation.

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
• Planning and deploying a current SiteCake website

• Softaculous installation workflow
• Softaculous cms catalogue
• Bolt project installation