centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-03-27 14:28:47 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update 07_multi_container.md (#23010)

Browse Source 
Update blog post URL.

## Description
The blog post link detailing why using env vars in production is
discouraged, is broken.
Updated link to blog post to post's new location.
This commit is contained in:
Marco Enrico
2025-07-07 15:08:04 +08:00
committed by GitHub
parent dfdf90b6b1
commit f3123f0506
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/get-started/workshop/07_multi_container.md
View File

@@ -192,7 +192,7 @@ The todo app supports the setting of a few environment variables to specify MySQ
>
> While using env vars to set connection settings is generally accepted for development, it's highly discouraged
> when running applications in production. Diogo Monica, a former lead of security at Docker,
> [wrote a fantastic blog post](https://diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/)
> [wrote a fantastic blog post](https://blog.diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/)
> explaining why.
>
> A more secure mechanism is to use the secret support provided by your container orchestration framework. In most cases,