From 077cb0155fb6e8459b0c40dfd6d782bec09990b3 Mon Sep 17 00:00:00 2001 From: Mark Harrison Date: Mon, 18 Nov 2024 19:24:03 +0000 Subject: [PATCH] Update variables.md --- src/pages/docs/best-practices/deployments/variables.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/pages/docs/best-practices/deployments/variables.md b/src/pages/docs/best-practices/deployments/variables.md index dea1de75ab..4b3cef17cc 100644 --- a/src/pages/docs/best-practices/deployments/variables.md +++ b/src/pages/docs/best-practices/deployments/variables.md @@ -1,7 +1,7 @@ --- layout: src/layouts/Default.astro pubDate: 2023-01-01 -modDate: 2023-10-04 +modDate: 2023-11-18 title: Variable Recommendations description: Guidelines and recommendations for configuring variables in Octopus Deploy. navOrder: 60 @@ -74,8 +74,6 @@ For configurations that differ per environment, our recommendation is to use a c Octopus Deploy can set an environment variable or configuration value during deployment to indicate which environment-specific configuration file to use. Or, if you are using .NET Framework, you can leverage [configuration file transforms](/docs/projects/steps/configuration-features/configuration-transforms). -For other items, - ## Variable Sets [Variable Sets](/docs/projects/variables/library-variable-sets) are a great way to share variables between projects. We recommend the following when creating variable sets.