Journal / topic tag
A focused reading collection for deployment.
This tag follows a change from approved source to a running result. The articles connect build inputs, release output, credentials, environment configuration, and verification, so deployment becomes a process someone else can reproduce. Choose a read according to what you serve: static files, a content management system, or an application with persistent state. Keep the source revision visible in release records so a later problem can be investigated.
Start with the hosting and deployment hub to identify that boundary. Then use static website deployment or framework deployment to examine the matching release path. As you read, write down how the previous usable version would be restored and what data must remain compatible with it.
Move from a repository to a reliable public website with a repeatable build, a reviewed artifact, purposeful preview checks, and a rollback plan that accounts for both HTML and cached assets.
The same Git repository workflow can lead to very different production systems. Compare what Hugo, Django, and a PHP application on LAMP require, then design releases around each stack’s build, runtime, and persistent data.
Understand how a Git release reaches visitors through Nginx and a CDN. Set explicit routing and cache policies, keep private source outside the web root, and verify changes at the public edge.