Open clairernovotny opened 8 years ago
Your naming convention proposal would work. Though this should be developed. If you want to differentiate now, with the current version of the task, you should use an Environment per site. Each environment can have it's own parameters.
Hi,
If I have multiple sites/services that I want to deploy as part of a release, and I want to update different settings for each one, I need a way to specify which variables go to which site.
One suggestions? How about a "prefix" parameter to the naming convention (optional/not required by default) that lets each instance of the build task specify a value.
Then you could have
site1.appsettings.somesetting
andsite2.appsettings.someothersetting
. In one build task instance, you'd specifysite1
as the prefix and in the other you'd putsite2
.Thoughts?