Uploaded July 2026 | Updated September 2026, 2 weeks ago
Check out Twingate and supercharge your security: bit.ly/3Y1OaZi
HomeLab secrets usually start simple: one `.env` file next to a Docker Compose stack. But over time, those secrets spread into GitLab variables, deployment scripts, copied folders, backups, notes, and places where they should not live.
In this video, I show a practical Infisical workflow for managing HomeLab and Docker secrets. We’ll install and configure Infisical, create a secrets project, explain environments like `dev`, `staging`, and `prod`, manage secrets in folders, sync secrets to GitLab, use the Infisical CLI, and inject secrets into a Docker Compose workflow without committing real values into a `.env` file.
I’ll also explain the caveats: Infisical is great as a central source of truth, but automated systems like CI/CD, Portainer, Arcane, Docker Compose, and other deployment tools still need a proper way to receive those secrets.
References:
- Infisical: infisical.com
- Infisical CLI Docs: infisical.com/docs/cli/overview
- Infisical Docker Compose Docs: infisical.com/docs/integrations/platforms/docker-compose
- Infisical Universal Auth Docs: infisical.com/docs/documentation/platform/identities/universal-auth
- Boilerplates: github.com/ChristianLempa/boilerplates
________________
💜 Support me and become a Fan! → youtube.com/channel/UCZNhwA1B5YqiY1nLzmM0ZRg/join
💬 Join our Community!
→ christianlempa.de/discord
👉 Follow me everywhere
→ christianlempa.de
________________
Read my Tech Documentation
christianlempa.de/docs
My Gear and Equipment
christianlempa.de/kit
________________
Timestamps:
00:00 Introduction
02:44 Overview and Docs
05:14 Install Infisical in Docker Compose
09:34 Set-Up and Configuration
11:31 Project Types
13:35 Managing Secrets
19:54 GitLab Sync
22:52 Infisical CLI
26:09 Use in Docker Compose
29:20 CI / CD integration
30:42 Final thoughts
________________
Links can include affiliate links.
Check out Twingate and supercharge your security: bit.ly/3Y1OaZi
HomeLab secrets usually start simple: one `.env` file next to a Docker Compose stack. But over time, those secrets spread into GitLab variables, deployment scripts, copied folders, backups, notes, and places where they should not live.
In this video, I show a practical Infisical workflow for managing HomeLab and Docker secrets. We’ll install and configure Infisical, create a secrets project, explain environments like `dev`, `staging`, and `prod`, manage secrets in folders, sync secrets to GitLab, use the Infisical CLI, and inject secrets into a Docker Compose workflow without committing real values into a `.env` file.
I’ll also explain the caveats: Infisical is great as a central source of truth, but automated systems like CI/CD, Portainer, Arcane, Docker Compose, and other deployment tools still need a proper way to receive those secrets.
References:
- Infisical: infisical.com
- Infisical CLI Docs: infisical.com/docs/cli/overview
- Infisical Docker Compose Docs: infisical.com/docs/integrations/platforms/docker-compose
- Infisical Universal Auth Docs: infisical.com/docs/documentation/platform/identities/universal-auth
- Boilerplates: github.com/ChristianLempa/boilerplates
________________
💜 Support me and become a Fan! → youtube.com/channel/UCZNhwA1B5YqiY1nLzmM0ZRg/join
💬 Join our Community!
→ christianlempa.de/discord
👉 Follow me everywhere
→ christianlempa.de
________________
Read my Tech Documentation
christianlempa.de/docs
My Gear and Equipment
christianlempa.de/kit
________________
Timestamps:
00:00 Introduction
02:44 Overview and Docs
05:14 Install Infisical in Docker Compose
09:34 Set-Up and Configuration
11:31 Project Types
13:35 Managing Secrets
19:54 GitLab Sync
22:52 Infisical CLI
26:09 Use in Docker Compose
29:20 CI / CD integration
30:42 Final thoughts
________________
Links can include affiliate links.
