Server operations · Lesson 8 of 36 · 8 minutes

Nginx site map

Inspect training nginx site layout and run a config test.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
List available sites
Run ls /etc/nginx/sites-available.
Hint & worked example
List directory entries; -a includes hidden names and -l adds ownership and permission detail.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ls /etc/nginx/sites-available
```
Remember: A listing is not proof that you can read or modify every listed file.
2
Read site config
Run cat /etc/nginx/sites-available/learn.conf.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cat /etc/nginx/sites-available/learn.conf
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
3
Test nginx
Run nginx -t.
Hint & worked example
Check the simulated configuration using nginx -t before changing service state.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
nginx -t
```
Remember: This lab checks a limited configuration subset, not the complete Nginx parser.

Understand the pattern

Nginx routing bugs often come from the wrong file being enabled.

ls: List directory entries; -a includes hidden names and -l adds ownership and permission detail.
A listing is not proof that you can read or modify every listed file.
cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
nginx: Check the simulated configuration using nginx -t before changing service state.
This lab checks a limited configuration subset, not the complete Nginx parser.

Worked example and expected result

$ ls /etc/nginx/sites-available

learn.conf

Exit status: 0. The command completed successfully in the training fixture.

$ cat /etc/nginx/sites-available/learn.conf

server {
  listen 443 ssl;
  server_name learn.clairos.ai;
  root /srv/www;
  location ^~ /api/learn/ { proxy_pass http://127.0.0.1:8010; }
  location ^~ /api/ { return 404; }
  add_header Content-Security-Policy "default-src 'self'; connect-src 'self'" always;
  # training config only
}

Exit status: 0. The command completed successfully in the training fixture.

$ nginx -t

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Nginx site map”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Reading a source file should precede changing it; avoid printing real secrets.

Apply it elsewhere

Before adapting the cat workflow from “Nginx site map” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Ports and processes Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual