Tools
Vercel — deploying frontends
Projects, preview deployments, domains, env, Next.js, and GitHub integration.
- 018 minWhat Vercel is and its deployment modelintro
An introduction to Vercel: a platform for the frontend, the Git-driven model, and how it differs from classic hosting.
- 0210 minFirst deploy of a Next.js applicationcore
Step by step: from a GitHub repository to a running Next.js application on Vercel.
- 039 minPreview deployments and the Pull Request workflowcore
How Vercel builds a preview for every PR and how to weave it into the ProfessNet code review process.
- 0410 minEnvironment variables and secretscore
How to safely manage variables and secrets in Vercel and tell public variables apart from confidential ones.
- 0510 minCustom domains and DNS configurationcore
Connecting a custom domain to a project on Vercel and correctly setting the DNS records.
- 069 minGitHub integration, build, and logsadvanced
How the Vercel↔GitHub integration works, how to read build and runtime logs, and diagnose failed deploys.
Check your knowledge — quiz
5 questions · pass mark 80%. Score saved locally.
1.What does Vercel do when you push to a branch other than main?
2.Which variable prefix in Next.js makes its value end up in the browser bundle and visible to every user?
3.Why can't a CNAME record be set for the root (apex) domain, e.g. professnet.pl?
4.Why do you need to redeploy after changing an environment variable in Vercel?
5.When a build passes locally but fails on Vercel, which command most faithfully reproduces Vercel's environment?