Maker Linux and VPS Flashcards

It proves the current working directory so path-sensitive commands are not run from the wrong project folder.

Use it to inspect names, sizes, owners, permissions, and hidden files before editing or copying.

It gives a bounded file inventory without crawling the whole machine.

It makes later commands and screenshots easier to explain or review.

Assuming the shell is inside the project root because the terminal was there earlier.

Check whether it is relative or absolute and whether it points at the generated release.

They establish location and file shape without changing the project.

It previews the top of a file without dumping the whole file into the terminal.

Line numbers, so the matching line can be reviewed or discussed precisely.

Recent lines usually show the current failure without reading the entire log file.

It identifies file type and can expose CRLF or binary content mistakes.

Read the relevant lines and write down the expected setting.

Seeing the right text in one file while the live service uses a different file.

It avoids a slow broad filesystem scan when nearby files are enough.

It walks each path component and shows whether a parent directory blocks traversal.

Mode, owner, group, and name for the exact file being inspected.

It changes too much and can hide the specific permission problem.

Nginx may find the path but fail to traverse or read one component.

Which user the service runs as and which path component has the mismatch.

The file can be readable while a parent directory lacks execute permission.

Inspect the path and owner/mode before changing anything.

nginx -t should pass so a syntax error does not break the server.

Which hostnames match a server block.

Which directory Nginx serves files from for that block.

It checks local Nginx routing for a specific hostname.