Pre-launch Checklist for Hosting and Cloud Server Selection: Item-by-Item Verification

The goal of the hosting launch check is to ensure the website can be accessed, restored, monitored, and scaled. Don't just check if the homepage loads; logins, …

Insights:Pre-launch Checklist for Hosting and Cloud Server Selection: Item-by-Item Verification

1. System and Environment

  • OS version, timezone, and character set are correct.
  • PHP/runtime version matches the local environment.
  • Extensions and dependencies are installed.
  • Sufficient disk space with a writable log directory.
  • Firewall only opens necessary ports.

2. Web and Site

  • Domain resolves to the correct IP address.
  • Site root directory, pretty URLs, upload size limit, and timeouts are configured correctly.
  • Homepage, category pages, detail pages, and 404 page load normally.
  • Admin panel is accessible with effective permission levels.

3. Database

  • Database version and connection count meet expectations.
  • Account uses minimal privileges; do not connect as root for business purposes.
  • Slow query log is enabled.
  • Table structures and indexes have been verified.
  • Backups are restorable.

4. Domain and HTTPS

  • Certificate domain matches and has not expired.
  • HTTP correctly redirects to HTTPS.
  • No mixed content warnings.
  • Auto-renewal tasks are functional.
  • DNS records and TTL values are reasonable.

5. Cache and CDN

  • Static asset cache rules are correct.
  • Page cache only covers cacheable pages.
  • Login, form, and payment pages are excluded from caching.
  • CDN origin pull and cache purge work properly.
  • A rollback switch is available.

6. Backup and Recovery

  • Code, database, and uploaded files are backed up separately.
  • Offsite backup replicas exist.
  • Retention period meets business needs.
  • A recovery drill has been performed.
  • Recovery time has been recorded.

7. Monitoring and Alerts

  • Availability monitoring.
  • CPU, memory, disk, and bandwidth metrics.
  • Certificate expiration alerts.
  • Alert on backup task success/failure.
  • Alerts reach people, not just email.

8. Security

  • Strong passwords in the admin panel; limit login attempts.
  • Restrictions on upload types and file sizes.
  • Error pages must not expose paths.
  • Sensitive configs kept out of the code repo.
  • Logs retained for traceability.

Within 24 Hours After Launch

  • Check error logs and access logs.
  • Monitor response times and 5xx errors.
  • Test forms and email delivery once.
  • Run a backup task test once.
  • Record baselines for easier comparison next time.

In Short

A post-launch check isn't about clicking through pages—it's about confirming that every critical capability has an owner, a rollback plan, and evidence.

Related Reading: