You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am frustrated that I cannot configure the container project to the same level as my on-premise project. There is far more flexibility is prefix naming conventions.
REQUEST
Add parameter to ComposeInit.ps1 for $SqlDatabasePrefix
Add parameter to ComposeInit.ps1 for $SqlCommerceDatabasePrefix
Add parameter to ComposeInit.ps1 for $SolrCorePrefix
Add parameter to ComposeInit.ps1 for $SolrCommerceCorePrefix
There already exists, in the .env file, options to customize these values. However, they cannot be provided through the parameters sent to the ComposeInit.ps1 script. I had to write a PowerShell script to overwrite these values before running the ComposeInit.ps1. Here is the script I am using:
The commerce database prefix is the big problem. I searched and replaced all instances of SitecoreCommerce_ with xxx.SitecoreCommerce_ to force the 3 commerce databases to have a prefix. It did not work. No matter what I do to the configuration files it always attaches with the standard naming. I believe there is something in the docker image which is hard coded. Notice the screenshot, no prefixes.
The text was updated successfully, but these errors were encountered:
I am frustrated that I cannot configure the container project to the same level as my on-premise project. There is far more flexibility is prefix naming conventions.
REQUEST
There already exists, in the .env file, options to customize these values. However, they cannot be provided through the parameters sent to the ComposeInit.ps1 script. I had to write a PowerShell script to overwrite these values before running the ComposeInit.ps1. Here is the script I am using:
The commerce database prefix is the big problem. I searched and replaced all instances of SitecoreCommerce_ with xxx.SitecoreCommerce_ to force the 3 commerce databases to have a prefix. It did not work. No matter what I do to the configuration files it always attaches with the standard naming. I believe there is something in the docker image which is hard coded. Notice the screenshot, no prefixes.
The text was updated successfully, but these errors were encountered: