Planning and deploying a current SilverStripe website

Review the current release requirements and Composer workflow. Plan a supported PHP/database combination and a deployment layout that exposes only the intended public directory.

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. Choose a supported release and verify its PHP, database and extension requirements. Prepare an empty project directory or an isolated staging copy.
2. Use the official Composer project workflow for a new site. For an existing project, deploy its reviewed source and locked dependencies instead of creating another application over it.
3. Set the web-server document root to the project's public directory. Keep environment configuration in the project root outside that public directory.
4. Configure the database and scoped credentials in the private environment settings. Select the appropriate environment mode; production must not expose developer diagnostics.
5. Review the release's database-build procedure. It changes schema, so use an empty intended database for a new installation, or a verified backup and tested migration for an existing site.
6. Create secure administrator access and test the CMS before directing visitors to the new deployment.

Example: /home/ACCOUNT/sites/example/public serves the website, while /home/ACCOUNT/sites/example/.env remains outside its public root. Confirm that private project files cannot be downloaded. A development server is not the production hosting configuration.

Install from the current trusted project package when an installer build is unsuitable. Configure environment settings outside public downloads, create the database with a scoped user and perform the documented schema/build step.

Create a sample page and asset, test a limited editor and check published URLs. Confirm the production environment does not expose debug information or private configuration.

Schema builds can change data structures. Back up the database and test custom code before deploying a framework or CMS upgrade, and keep a rollback compatible with the database changes.

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 Bolt website

• Softaculous installation workflow
• Softaculous cms catalogue
• Silverstripe getting started