Deploying a PHP/MySQL Website on GreatHosts

1. Check the application requirements

Read the project requirements before changing the hosting environment. Confirm the PHP version range, required extensions, database engine/version, writable directories and whether the application expects scheduled tasks.

• GreatHosts currently exposes PHP versions through 8.5.
• MySQL choices verified in the environment are 5.7, 8.0 and 8.4.
• OPcache and Imagick are available.
• Custom php.ini control is available.
• Cron jobs are available.

2. Upload the application files

Use GreatHosts CP File Manager to upload files or a ZIP archive. The hosting home path is /home/www and a domain normally maps to /home/www/domain.com. Put the application’s public entry point at the web root expected by the project.

• Keep configuration backups before replacing an existing site.
• Extract archives server-side instead of uploading thousands of individual files when practical.
• Check file and directory permissions after extraction.

3. Create and import the database

Create the database and database user from GreatHosts CP. Import the SQL dump, then configure the application to use localhost as the database host. Use a dedicated database user rather than reusing unrelated credentials.

• Match the application’s expected character set/collation.
• Use the MySQL version supported by the application.
• For large imports, split or compress the dump if the normal browser upload limit becomes a constraint.

4. Configure PHP deliberately

Select a compatible PHP version and change php.ini only when the application actually requires it. Avoid increasing memory, upload or execution limits blindly; first identify the operation that needs the change.

• Enable production error handling rather than displaying stack traces to visitors.
• Use OPcache for normal production PHP execution.
• Confirm required extensions rather than assuming they are loaded.
• Keep application secrets outside publicly served files whenever possible.

5. Configure scheduled jobs if required

If the application has a scheduler, queue runner or maintenance command that can be expressed as a cron task within the shared environment, configure it in GreatHosts CP. Applications that require a permanently running system service may be better suited to KVM VPS.

6. Enable HTTPS and test

Point the domain correctly, issue the applicable certificate, then switch application URLs to HTTPS. Test login, database writes, uploads, email, redirects and 404 behavior before considering the migration complete.

• Free Let’s Encrypt applies to qualifying domains ordered through GreatHosts.
• Paid SSL certificates are annual products.
• Check application base URLs after moving from a local/staging environment.

7. Troubleshoot by evidence

Use application logs, PHP errors and browser/network errors to isolate a problem before changing hosting tiers. A 500 error is not evidence that the server is too small; it is often configuration, permissions, missing extensions or application code.

• Reproduce the exact failing request.
• Check the corresponding log entry.
• Verify PHP version and extensions.
• Verify database credentials and host.
• Escalate to support with the error and timestamp when the hosting layer appears responsible.

Services related to this guide