Deployment
Taking one specific build of your app and installing it into one target environment: production, staging, or a preview URL.
See it
What it is
A deployment takes one specific build (a commit, a bundle, a container image) and installs it into one specific environment so it starts serving traffic. Two words matter: specific build and specific environment. 'Deploy the fix' really means 'take build abc123 and make production run it instead of build xyz789'.
In practice it is a handful of steps a platform does for you: install dependencies, run the build command, upload the output, point traffic at the new version, keep the old one around in case it goes badly. Vercel, Netlify, Fly, and Render collapse all of that into a git push. Kubernetes and friends make each step explicit.
Gotcha: a deploy is not just code. Environment variables, database migrations, and cached assets ship on their own schedules, and most 'it worked locally' incidents come from one of those three drifting out of sync with the build you just pushed.
Ask AI for it
Set up a deployment for this app to a managed host (Vercel, Netlify, or Fly). Detect the framework and package manager, define the install and build commands and the output directory, list every environment variable the app reads with a note on which environment needs it, add a post-deploy smoke check that requests the homepage and a health endpoint, and document the exact command to redeploy and to promote a previous build back to live.