Name what you already understand before the build gets bigger.
Web deployment
Nginx Static Site Basics for Makers
Learn how Nginx serves a static site from a document root, why release folders help, and how to verify a deploy safely.
Topic goal to ladder route
Know the destination, then climb the route.
A topic is the maker goal. A ladder is the route from what you understand now to one visible proof you can build, sketch, test, or explain. This one ties back to Deploy a Static Site on a VPS.
Understand the path from a local HTML file to a live HTTPS page on a VPS.
Read the short lesson, watch one source tutorial, sketch the idea, check the math, then practice.
Sketch a release layout with releases/YYYYMMDDTHHMMSSZ and current. Explain how rollback would work.
Ladder steps
Each step should prove one idea before the project asks for the next one.
Separate releases from currentUse timestamped release folders and a current symlink to make rollback possible. readlink -f current shows the active release.
Know the document rootThe root directive tells Nginx which folder becomes the web root. The requested URL maps to a file under root.
Test before reloadNginx can validate syntax before traffic changes. nginx -t must pass before systemctl reload nginx.
Verify from outsidecurl checks the public path, not just local files. HTTP 200 and expected text confirm the page served.
Examples to inspect
Use examples to read signals, not as blind recipes.
Test Nginx configuration
Project signal
sudo nginx -t
Expected signal: syntax is ok and test is successful
Show the active release folder
Project signal
readlink -f /srv/www/site/current
Expected signal: A timestamped release path
Check public response headers
Project signal
curl -I https://example.com/
Expected signal: HTTP/2 200 or HTTP/1.1 200
Common traps
- Reloading before nginx -t.
- Editing the live release in place.
- Confusing a local file preview with a public deploy.
Practice task
Sketch a release layout with releases/YYYYMMDDTHHMMSSZ and current. Explain how rollback would work.
Next steps
- Connect DNS.
- Add TLS after HTTP works.
- Use Git to track deploy changes.
Practice path
- Near-Copy Rebuild: Recreate one example, decision path, or worked explanation from Nginx Static Site Basics for Makers. Keep most givens the same, then apply, explain, and check while naming each cue you used. Use the lesson's example block when it helps.
- One-Change Transfer: Change exactly one condition, number, input, symptom, material, or constraint from the near-copy case. Then apply, explain, and check again and explain what changed.
- Mixed Review Set: Interleave this topic with one prerequisite or adjacent idea. Write three short prompts: one recall, one application, and one comparison.
- Find And Fix The Error: Invent a plausible wrong answer, unsafe step, invalid assumption, or bad classification. Mark the first point where it goes wrong, then correct it using the lesson's check.
Flashcard preview
Why use a current symlink?
It lets a deploy switch atomically and makes rollback simpler.
What does the 'Separate releases from current' step prove?
Use timestamped release folders and a current symlink to make rollback possible. Check: readlink -f current shows the active release.
What does the 'Know the document root' step prove?
The root directive tells Nginx which folder becomes the web root. Check: The requested URL maps to a file under root.
What does the 'Test before reload' step prove?
Nginx can validate syntax before traffic changes. Check: nginx -t must pass before systemctl reload nginx.
What does the 'Verify from outside' step prove?
curl checks the public path, not just local files. Check: HTTP 200 and expected text confirm the page served.
When would you use `sudo nginx -t`?
Use it to test nginx configuration. Expected signal: syntax is ok and test is successful
Downloadable study pack
Export the same lesson as a plain Markdown note or Anki-compatible TSV. Commands and code blocks stay plain so they work in local notes.
Related paths
Study pack check passed. Notes, cards, examples, and practice tasks are meant to keep the lesson useful outside the page.
Connected routes
Use these links like a project map: what helps before this, what this unlocks, and where it fits.
Helpful before this
Project context
What this unlocks
- Connect DNS.
- Add TLS after HTTP works.
- Use Git to track deploy changes.
Related pages
Text lesson and video notes
This page works as a text lesson first. If you later watch a matching tutorial, use the notes pattern here to capture the build decision, timestamps, warnings, and the next practical task instead of saving a raw link.
Read the text lesson
Use the steps, examples, traps, and practice task on this page to understand the next move in a maker project.
Attach a video note
Save useful workshop or tutorial videos into an Obsidian note with timestamps, source links, and what each segment proves. The site does not need the video to be useful.
Review and practice
Download the cards, then finish the practice task before adding more links to your project notebook.
Source video for this ladder
Use the video as source material for notes, cards, and practice. The written ladder still works without playback.
Use the source as a companion, not as a replacement for the written ladder.
Featured tutorial
Primary source
Linux File Permissions in 5 Minutes
Video by Travis Media ยท Open on YouTube
A compact visual explanation of ownership and permission bits that supports deployment, file repair, and project servers.
Source note saves on this device.
Suggest a better source video
If another tutorial explains this topic more clearly, send the title and YouTube URL. Suggestions should help the ladder, not replace it.
Topic: Nginx Static Site Basics for Makers
Continue learning this topic
Use this page as part of a project path, not as a one-off article. Save the note, review the cards, try the practice task, then choose the next lesson based on what your project exposes.
Study assets
Project context
- Deploy a Static Site on a VPS
- Browse Software and Linux
- Next ladder clue: Connect DNS.
Related references
Buy me a cup of coffee
TopicLadder is free to read. Coffee support helps turn rough maker ladders into clearer project paths, notes, cards, and practice labs.
