-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestions for Sitecore xP3 configuration #11
Comments
Hey @danteciambella If you need a clean Sitecore configured to work in scaled environment, you don't need to modify the ScalabilitySettings.config as everything is done already. Mixture of I cannot advise on UAT and Development as I do not understand what is it - for me it sounds like different environments, but it also means they have to be completely separate and have to use different sets of databases. |
Hey @AlenPelin thank you for your answer. |
Sorry I closed the issue accidently |
Sitecore does not support having more than 1 standalone role in 1 environment. So I highly recommend to have these instances in different environments.
Valid question. No need. |
This project is intended to eliminate any changes to default configuration files. Taking into account that |
I would like to use the configuration roles package for a Sitecore xP3 production (2CD + 1 CM + 1 UAT + 1 Development).
I'm tring the configuration role package and, if I'm not wrong, I need to manually configure the scalability file (ScalabilitySettings.config) to set the two different CD name. Please in your opinion there are some other configuration that I need to do manually after I installed the package in each role?
If I'm not wrong I need to configure the web.config Role file in the following way:
<add key="role:define" value="ContentManagement|Processing|Reporting" />
<add key="role:define" value="ContentDelivery" />
<add key="role:define" value="ContentDelivery" />
<add key="role:define" value="Standalone" />
<add key="role:define" value="Standalone" />
Thanks in advance.
Dante.
The text was updated successfully, but these errors were encountered: