Environment Variables Explained From the Operating System up

Your app never reads the .env file. It reads its environment: a list of name=value lines the operating system hands to a process the moment it starts. This video builds that up from first principles: what a process is, how a parent starts a child with fork and exec, where the environment list comes from, what dotenv actually does, and why any parent (your shell, systemd, Docker, the kubelet) can fill that list. Then it shows the alternative to a secrets file on every laptop: runtime injection with the Infisical CLI. Chapters 0:00 The .env file 0:33 The app 0:57 Secret sprawl 1:46 Where the value comes from 2:44 What a process is 3:36 Fork and exec 4:22 What the environment is 5:22 Where the parent gets its list 6:13 What dotenv is 6:45 Every language reads the same list 6:54 Any parent will do 7:10 Runtime injection 8:26 Where the secret is 8:41 Back to the problem 9:05 Recap Follow Infisical: Website: https://infisical.com LinkedIn: https://www.linkedin.com/company/infisical GitHub: https://github.com/Infisical Twitter / X: https://x.com/infisical Slack: https://infisical.com/slack