Nano and editing · Lesson 19 of 27 · 8 minutes

Nano config copy

Copy config into lab before editing notes.

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
Copy config
Run cp /etc/nginx/sites-available/learn.conf lab/learn.conf.copy.
Hint & worked example
Copy a file to a new location, leaving the original in place.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cp /etc/nginx/sites-available/learn.conf lab/learn.conf.copy
```
Remember: Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
2
Open copied config
Run nano lab/learn.conf.copy. Save a nonempty note using the worked example below. Required evidence: # reviewed training copy.
Hint & worked example
Edit a virtual text file using the browser editor and explicitly save it.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
nano lab/learn.conf.copy
```
Save this example in the editor:
```
server {
  listen 443 ssl;
  server_name learn.clairos.ai;
  root /srv/www;
  # reviewed training copy
}
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
3
Compare config copy
Run diff /etc/nginx/sites-available/learn.conf lab/learn.conf.copy.
Hint & worked example
Compare two text files; a difference is a meaningful nonzero status, not necessarily an execution error.
Inspect the differences. diff exits 1 when files differ and 0 when they match.
```
diff /etc/nginx/sites-available/learn.conf lab/learn.conf.copy
```
Remember: Status 1 means differences for diff; shell status must be interpreted in command context.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

cp: Copy a file to a new location, leaving the original in place.
Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
nano: Edit a virtual text file using the browser editor and explicitly save it.
Opening the editor does not complete a write task. Save and verify the contents.
diff: Compare two text files; a difference is a meaningful nonzero status, not necessarily an execution error.
Status 1 means differences for diff; shell status must be interpreted in command context.

Worked example and expected result

$ cp /etc/nginx/sites-available/learn.conf lab/learn.conf.copy

(no output; exit 0)

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

$ nano lab/learn.conf.copy

Opening simulated nano for /home/learner/lab/learn.conf.copy. Save or cancel in the browser.

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

$ Save the editor buffer

server {
  listen 443 ssl;
  server_name learn.clairos.ai;
  root /srv/www;
  # reviewed training copy
}

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

$ diff /etc/nginx/sites-available/learn.conf lab/learn.conf.copy

--- /etc/nginx/sites-available/learn.conf
+++ /home/learner/lab/learn.conf.copy
-  location ^~ /api/learn/ { proxy_pass http://127.0.0.1:8010; }
+  # reviewed training copy
-  location ^~ /api/ { return 404; }
+}
-  add_header Content-Security-Policy "default-src 'self'; connect-src 'self'" always;
+
-  # training config only
+
-}
+

Exit status: 1. This nonzero result is an expected part of this exercise.

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 “Nano config copy”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Opening the editor does not complete a write task. Save and verify the contents.

Apply it elsewhere

Before adapting the nano workflow from “Nano config copy” 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: Nano rollback note 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