A Developer's Guide to Unix File Permissions (Finally Makes Sense)

Every developer hits that moment: you deploy to a server, and suddenly nothing works because of permission errors. You Google "chmod 777" and paste it in. It fixes the problem — and creates ten new ones. Let's break down Unix file permissions so you actually understand what you're doing. The Permission Model Every file and directory in Unix has three permission groups: Owner (u) — the user who owns the file Group (g) — users in the file's group Others (o) — everyone else Each group gets three permission types: Read (r) — view file contents or list directory Write (w) — modify file or create/delete files in directory Execute (x) — run file as program or access directory Reading ls -l Output When you run ls -l , you see something like: -rwxr-xr-- 1 deploy www-data 4096 Mar 9 config.yml That first column breaks down as: - rwx r-x r-- │ │ │ │ │ │ │ └── Others: read only │ │ └─────── Group: read + execute │ └──────────── Owner: read + write + execute └─────────────── File type (- = file, d