- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
Environment Variables and .env Files (the session trap + the secrets rule)
Some values change between runs — the database URL, your API key, the port your app binds to. The code that USES those values stays the same. The split between code and config is what environment variables are for.
This lesson is the two ways to set them, the trap that catches everyone
the first time, and the one rule that keeps your API keys off GitHub.
What it covers:
• How code reads env vars — process.env.VARIABLE_NAME
• Way 1 — export, in your shell: sets it for the current terminal session
• THE TRAP — close the terminal and it's gone. "I set it, why isn't it
working?" The answer: you set it in a different session.
• Way 2 — .env, in your project root: frameworks read it automatically on
every run
• The hard rule — never commit .env. Once a secret is in git history, it's
effectively public. GitHub indexes it; bots scrape it.
• When to use each — export for one-offs, .env for everything else,
always .env for secrets.
If you remember nothing else from this lesson: an API key written into your
code is an API key on GitHub. Secrets live in env vars, never in source
code. That isn't style — it's the only way to keep the secret a secret.
This is Lesson 2 of the Environment Basics module in Vibe Engineering — a
school that teaches engineering fundamentals to people who build with AI.
Vibe coding gets you a demo. Vibe Engineering gets you a product you own.
▶ Earlier in this module:
1. What the Environment Is — [link]
— Chapters —
0:00 Why env vars exist
0:22 How code reads them (process.env)
0:54 Way 1: export (per terminal session)
1:16 The session trap — close the terminal, it's gone
1:36 Way 2: .env (per project, every run)
1:56 Never commit .env
2:14 When to use each — and the frame
Free lessons and the full curriculum: https://www.skool.com/vibe-engineering-9169
#vibecoding #aicoding #environment #devops #softwareengineering #buildinpublic
Видео Environment Variables and .env Files (the session trap + the secrets rule) канала breakit_makeit
This lesson is the two ways to set them, the trap that catches everyone
the first time, and the one rule that keeps your API keys off GitHub.
What it covers:
• How code reads env vars — process.env.VARIABLE_NAME
• Way 1 — export, in your shell: sets it for the current terminal session
• THE TRAP — close the terminal and it's gone. "I set it, why isn't it
working?" The answer: you set it in a different session.
• Way 2 — .env, in your project root: frameworks read it automatically on
every run
• The hard rule — never commit .env. Once a secret is in git history, it's
effectively public. GitHub indexes it; bots scrape it.
• When to use each — export for one-offs, .env for everything else,
always .env for secrets.
If you remember nothing else from this lesson: an API key written into your
code is an API key on GitHub. Secrets live in env vars, never in source
code. That isn't style — it's the only way to keep the secret a secret.
This is Lesson 2 of the Environment Basics module in Vibe Engineering — a
school that teaches engineering fundamentals to people who build with AI.
Vibe coding gets you a demo. Vibe Engineering gets you a product you own.
▶ Earlier in this module:
1. What the Environment Is — [link]
— Chapters —
0:00 Why env vars exist
0:22 How code reads them (process.env)
0:54 Way 1: export (per terminal session)
1:16 The session trap — close the terminal, it's gone
1:36 Way 2: .env (per project, every run)
1:56 Never commit .env
2:14 When to use each — and the frame
Free lessons and the full curriculum: https://www.skool.com/vibe-engineering-9169
#vibecoding #aicoding #environment #devops #softwareengineering #buildinpublic
Видео Environment Variables and .env Files (the session trap + the secrets rule) канала breakit_makeit
Комментарии отсутствуют
Информация о видео
7 июня 2026 г. 5:23:38
00:02:53
Другие видео канала





















