From 9cc2e366c3bb20f20d5787d3c7a2e0b63622dfe2 Mon Sep 17 00:00:00 2001 From: Marco Enrico Date: Sat, 5 Jul 2025 23:15:24 +0800 Subject: [PATCH] Update 07_multi_container.md Update blog post URL. --- content/get-started/workshop/07_multi_container.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/get-started/workshop/07_multi_container.md b/content/get-started/workshop/07_multi_container.md index aab577adeb3a..e08b970bbd72 100644 --- a/content/get-started/workshop/07_multi_container.md +++ b/content/get-started/workshop/07_multi_container.md @@ -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,