Git in One Page: A Quick Summary
The whole Git picture in a few minutes: commits, branches, merging, rebase, reset, remotes, tracking and config, then a short list of everyday commands. Links to the full explanations.
The whole Git picture in a few minutes: commits, branches, merging, rebase, reset, remotes, tracking and config, then a short list of everyday commands. Links to the full explanations.
All of Git on one page, with a quick concept refresher above every group of commands: names and refs, undo, stash, merge, squash, rebase, cherry-pick, remotes, tracking, config, identity, force push, Gerrit, recipes, and what each error message really means.
Once commits and branches are clear, remotes are easy: what origin really is, what origin/main is, how fetch, pull and push move pointers, what refs/heads means, tracking, git reset --hard to any remote, and using several repositories from one folder.
Git explained from the very start with simple pictures: what a commit is, why a branch is only a pointer, how HEAD works, how work branches out, and how fast-forward, three-way merge, rebase, squash and reset really play out.
What Caddy is, why you'd put it in front of Nginx for internal HTTPS, and when Caddy alone is enough. Short Caddyfiles for both setups, how to trust its internal certificate, and what to check when it won't start.
The whole nginx series on one page: every concept as short points with one annotated config each, in learning order, linked to the full explanations. Then the lookup tables: phases, directives, variables, commands and error-to-cause troubleshooting.
One real config dissected: a location that proxies to whatever URL the request names. Directives vs built-in vs user-defined variables, $arg_*, set, proxy_pass with a variable, resolver and DNS at request time, Host and SNI towards the remote server, and SSRF.
The implementation side of gateway authentication: where auth belongs, who holds tokens and secrets, central identity with local permissions, login/refresh/logout and whoami endpoints, cookies, and integrating other teams' APIs and iframes.
DevTools shows an OPTIONS request your code never made, answered with methods your path doesn't even have. Who sends it, who answers it, and why the allowed-methods list comes from CORS configuration, not from your routes — the same story in every stack, from Django to Express to nginx.
Requests nginx makes to itself (internal, named locations, error_page, X-Accel-Redirect), auth_request and the request phases, who really authenticates, trust boundaries, and which directive changes which of the four messages.