Launching a New Website

This checklist provides guidance about what needs to be done before and during the release of a new web site. Also what part of the team that needs to be involved in each step.

At Least 3 Weeks Ahead

The reason for doing this quite early is to make sure the customer have time to schedule in any necessary work on their side.

1. Load Testing (devops)

   • Perform load testing to simulate expected traffic.
   • Identify and mitigate potential performance bottlenecks.

2. Check Server Requirements (devops + project manager)

   • Confirm server specifications with the customer (if they will host the site on their own servers).
   • Ensure the server can handle the anticipated traffic.
   • Plan for server upgrades if necessary.

3. Open Necessary Firewall Ports (devops + project manager)

   • Identify all required ports for web traffic, database access, etc.
   • Request the customer to open these ports on their firewall (if they will host the site on their own servers).

4. Backup Strategy (devops + project manager)

   • If customer is maintaining the server, make sure they have a backup system in place and have scheduled restore points just before launch.

5. Ip Restriction / Basic Auth (devops + project manager)

   • Give the customer the option to protect vulnerable endpoints such as /wp-admin either by ip restriction or by basic auth.
   • If they prefer ip restriction, ask them for a list of ip addresses to be whitelisted.

A Few Days Before Launch

These steps are conducted by devops engineer.

1. DNS Configuration (devops)

   • Ensure DNS records are correctly set up.
   • Plan the DNS cutover strategy to minimize downtime.

2. Security Measures (developer + devops)

   • Ensure all security patches are up-to-date.
   • Conduct a security audit to identify and fix vulnerabilities.

3. Continuous Integration/Continuous Deployment (CI/CD) Setup (devops)

   • Set up automated deployment pipelines in Jenkins.

4. Final Testing (developer + project manager + customer)

   • Conduct final functional testing.
   • Verify compatibility across different browsers and devices.

5. Content Review (developer + project manager + customer)

   • Ensure all content is up-to-date and correctly displayed.
   • Confirm that all media assets are properly optimized.

6. Monitor Setup (devops)

   • Set up monitoring tools to track site performance.
   • Configure alerts for critical issues (e.g., downtime, high latency).

7. Backup Confirmation (devops or customer IT dep)

   • Take a final backup of the current production site.
   • Verify the integrity of the backup.

8. Database Migration (devops)

   • Migrate the database to the new environment.
   • Ensure data integrity post-migration.

Launch Day

1. Pre-Launch Checklist (devops + project manager)

   • Confirm DNS settings.
   • Verify server health and resource availability.
   • Ensure all stakeholders are informed about the launch schedule.

2. Deployment (devops)

   • Deploy the latest version of the website to the production server.
   • Verify successful deployment without errors.

3. Post-Deployment Testing

   • Ensure critical functionalities are working (developer, devops + project manager, customer).
   • Verify site performance under real traffic conditions (devops).

4. Monitoring and Support (developer + devops)

   • Monitor the site closely for any issues.
   • Be prepared to rollback if critical issues arise.
   • Provide support for any immediate post-launch issues.

5. Communicate Launch Success (devops / project manager)

   • Inform stakeholders that the launch is complete.