Learn · Deployment & hosting
Deployment is the process of taking code from a developer's computer and putting it live on a server so real users can access it. It covers moving the files, configuring the environment, and switching the site over, ideally with no downtime. "Shipping" a change means deploying it.
Modern deployment is usually automated. Instead of manually copying files, a pipeline takes approved code, runs its tests, and releases it, which is faster and less error-prone than doing it by hand. This is the delivery half of CI/CD.
The goal of good deployment is that releasing a change is routine and safe, not a nerve-wracking event. Automated, repeatable deployments with the ability to undo quickly are what let teams ship improvements often without fear.
Updated July 2026
Go deeper
Related
Typically: a developer commits code to version control, that triggers an automated pipeline which runs tests and builds the site, and if everything passes, the pipeline deploys it to the host, often first to staging and then to production. Modern setups make this near-instant and repeatable.
A rollback is reverting to the previous working version when a new deployment causes a problem. Instead of scrambling to fix a live issue, you switch back to the last good version in seconds, restoring service while you investigate calmly. The ability to roll back fast is a core safety net.
A staging environment is a private copy of your live site used to test changes safely before they go public. You deploy new work to staging first, check it there, and only then release it to production (the live site). It's the rehearsal space that keeps experiments away from real users.