EnvironmentName setting in config.json
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I noticed that the EnvironmentName settings is always (for each process) set to HabitatMinions.
What is the purpose of this setting?
(I could not find any official documentation about it)
Shouldn't it e.g. be set to HabitatAuthoring for the Authoring process in order to prevent triggering a minion task?
sitecore-commerce
add a comment |Â
up vote
1
down vote
favorite
I noticed that the EnvironmentName settings is always (for each process) set to HabitatMinions.
What is the purpose of this setting?
(I could not find any official documentation about it)
Shouldn't it e.g. be set to HabitatAuthoring for the Authoring process in order to prevent triggering a minion task?
sitecore-commerce
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I noticed that the EnvironmentName settings is always (for each process) set to HabitatMinions.
What is the purpose of this setting?
(I could not find any official documentation about it)
Shouldn't it e.g. be set to HabitatAuthoring for the Authoring process in order to prevent triggering a minion task?
sitecore-commerce
I noticed that the EnvironmentName settings is always (for each process) set to HabitatMinions.
What is the purpose of this setting?
(I could not find any official documentation about it)
Shouldn't it e.g. be set to HabitatAuthoring for the Authoring process in order to prevent triggering a minion task?
sitecore-commerce
sitecore-commerce
asked 4 hours ago


Joost
1615
1615
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
The EnvironmentName setting is used to identify which environment should be StartedUp on application startup.
The OOTB example wrongly has the HabitatMinions set as EnvironmentName for all roles. If you have this setting for all roles each will start a Minion task, which is bad for performance.
This is registered by Sitecore Support as bug with public reference number 41553.
add a comment |Â
up vote
1
down vote
Update from Sitecore Support this has been fixed in SIF: SIF.Sitecore.Commerce.1.2.14.zipModulesDeployCommerceContentDeployCommerceContent.psm1
...
# Set the proper environment name
$pathToJson = $(Join-Path -Path $PhysicalPath -ChildPath "wwwrootconfig.json")
$originalJson = Get-Content $pathToJson -Raw | ConvertFrom-Json
$environment = "HabitatShops"
if ($Name -match "CommerceAuthoring")
$environment = "HabitatAuthoring"
elseif ($Name -match "CommerceMinions")
$environment = "HabitatMinions"
$originalJson.AppSettings.EnvironmentName = $environment
$originalJson | ConvertTo-Json -Depth 100 -Compress | set-content $pathToJson
}
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
The EnvironmentName setting is used to identify which environment should be StartedUp on application startup.
The OOTB example wrongly has the HabitatMinions set as EnvironmentName for all roles. If you have this setting for all roles each will start a Minion task, which is bad for performance.
This is registered by Sitecore Support as bug with public reference number 41553.
add a comment |Â
up vote
3
down vote
The EnvironmentName setting is used to identify which environment should be StartedUp on application startup.
The OOTB example wrongly has the HabitatMinions set as EnvironmentName for all roles. If you have this setting for all roles each will start a Minion task, which is bad for performance.
This is registered by Sitecore Support as bug with public reference number 41553.
add a comment |Â
up vote
3
down vote
up vote
3
down vote
The EnvironmentName setting is used to identify which environment should be StartedUp on application startup.
The OOTB example wrongly has the HabitatMinions set as EnvironmentName for all roles. If you have this setting for all roles each will start a Minion task, which is bad for performance.
This is registered by Sitecore Support as bug with public reference number 41553.
The EnvironmentName setting is used to identify which environment should be StartedUp on application startup.
The OOTB example wrongly has the HabitatMinions set as EnvironmentName for all roles. If you have this setting for all roles each will start a Minion task, which is bad for performance.
This is registered by Sitecore Support as bug with public reference number 41553.
answered 4 hours ago


Joost
1615
1615
add a comment |Â
add a comment |Â
up vote
1
down vote
Update from Sitecore Support this has been fixed in SIF: SIF.Sitecore.Commerce.1.2.14.zipModulesDeployCommerceContentDeployCommerceContent.psm1
...
# Set the proper environment name
$pathToJson = $(Join-Path -Path $PhysicalPath -ChildPath "wwwrootconfig.json")
$originalJson = Get-Content $pathToJson -Raw | ConvertFrom-Json
$environment = "HabitatShops"
if ($Name -match "CommerceAuthoring")
$environment = "HabitatAuthoring"
elseif ($Name -match "CommerceMinions")
$environment = "HabitatMinions"
$originalJson.AppSettings.EnvironmentName = $environment
$originalJson | ConvertTo-Json -Depth 100 -Compress | set-content $pathToJson
}
add a comment |Â
up vote
1
down vote
Update from Sitecore Support this has been fixed in SIF: SIF.Sitecore.Commerce.1.2.14.zipModulesDeployCommerceContentDeployCommerceContent.psm1
...
# Set the proper environment name
$pathToJson = $(Join-Path -Path $PhysicalPath -ChildPath "wwwrootconfig.json")
$originalJson = Get-Content $pathToJson -Raw | ConvertFrom-Json
$environment = "HabitatShops"
if ($Name -match "CommerceAuthoring")
$environment = "HabitatAuthoring"
elseif ($Name -match "CommerceMinions")
$environment = "HabitatMinions"
$originalJson.AppSettings.EnvironmentName = $environment
$originalJson | ConvertTo-Json -Depth 100 -Compress | set-content $pathToJson
}
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Update from Sitecore Support this has been fixed in SIF: SIF.Sitecore.Commerce.1.2.14.zipModulesDeployCommerceContentDeployCommerceContent.psm1
...
# Set the proper environment name
$pathToJson = $(Join-Path -Path $PhysicalPath -ChildPath "wwwrootconfig.json")
$originalJson = Get-Content $pathToJson -Raw | ConvertFrom-Json
$environment = "HabitatShops"
if ($Name -match "CommerceAuthoring")
$environment = "HabitatAuthoring"
elseif ($Name -match "CommerceMinions")
$environment = "HabitatMinions"
$originalJson.AppSettings.EnvironmentName = $environment
$originalJson | ConvertTo-Json -Depth 100 -Compress | set-content $pathToJson
}
Update from Sitecore Support this has been fixed in SIF: SIF.Sitecore.Commerce.1.2.14.zipModulesDeployCommerceContentDeployCommerceContent.psm1
...
# Set the proper environment name
$pathToJson = $(Join-Path -Path $PhysicalPath -ChildPath "wwwrootconfig.json")
$originalJson = Get-Content $pathToJson -Raw | ConvertFrom-Json
$environment = "HabitatShops"
if ($Name -match "CommerceAuthoring")
$environment = "HabitatAuthoring"
elseif ($Name -match "CommerceMinions")
$environment = "HabitatMinions"
$originalJson.AppSettings.EnvironmentName = $environment
$originalJson | ConvertTo-Json -Depth 100 -Compress | set-content $pathToJson
}
answered 1 hour ago


Joost
1615
1615
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f13969%2fenvironmentname-setting-in-config-json%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password