Comments (5)
I don't know why you would deploy Unicorn configs to a role that isn't Standalone or ContentManagement is the reverse question 🙃
Generally the error you describe only appears if you deploy Unicorn configs to servers configured for the CD server role only. And the clear recommendation is, that Unicorn has no business at all being deployed to public facing server instances.
That said, if for some reason, you want to continue deploying Unicorn to CD, you would need to change this site definition role requirement. A better solution would be to just delete the Unicorn config on CD.
from unicorn.
@cassidydotdk while I completely agree with your philosophy, the file in question, Unicorn.config, includes a comment at the top stating:
This file should be present on all environments Unicorn is present on. It is safe to leave on Content Delivery servers, as it changes no stock Sitecore configuration.
for this reason, the file should be corrected so that it can in fact, be safe to leave on Content Delivery servers
from unicorn.
Actually it's the comment that's in error :-)
from unicorn.
I strongly feel that it can be inferred that the philosophy that these Unicorn configuration files are intended to work in all environments out-of-the-box, based on the fact that other configuration files already include explicit "role:require" attributes, indicating that the intention is to compensate for every potential role, including ContentDelivery.
I feel that it would support future adopters better to simply add the role:require as my original post had recommended, keeping to the same mantra appearing throughout the rest of the files. The expectation that developers would need to modify the base module out-of-the-box to prevent a 500 error in a common scenario seems undesirable.
from unicorn.
The philosophy of the Unicorn.config file is, that - like the product itself - it should work on Sitecore versions at least 8.0 through to today. role:require is not available prior to 9.x or so, I forget exactly when it was introduced by Sitecore.
There is not and has never been a "hands-off" approach to these configuration files. Some amount of tinkering was always required, whether it was to enable/disable certain files, remove certain files from deployment to specific environments, disabling the dataprovider for anything not local dev, and so on.
The fact that the top comment is misleading in Unicorn.config is an oversight from when the unicorn
site was introduced.
There are various ways people in the community goes about handling their setups. Here are a few.
- https://sitecore.stackexchange.com/a/26107/73
- https://praveenmanchanablog.wordpress.com/2020/03/02/unicorn-with-custom-rule-configurations/
You could also add a config file of your own, if you're uncomfortable modifying the supplied files. Using a patch:delete
to remove the unicorn
<site>
definition and insert your own with whatever role:require
you like.
from unicorn.
Related Issues (20)
- security Vulnerabilities in Unicorn.SharedSecret.config file HOT 1
- Dilithium + Unicorn.DataProvider.10.1 HOT 3
- Sitecore 10.1 uses Sitecore.Kernel 16.0.0.0 version which does not have attribute 'UsedImplicitlyAttribute' and unicorn uses this attribute HOT 3
- Syncing Unchecked Shared field checkbox is not performing the movement of data from SharedFields to VersionFields tables HOT 10
- Unicorn.aspx indicates Transparent Sync is enabled on configs but TS is not working and does not display in Content Editor warning HOT 4
- Unicorn.DataProvider.10.1.config role:require setting prevents the config from being loaded on XM0 HOT 2
- Error message during Unicorn Sync "The statement terminated. The maximum recursion 100 has been exhausted before statement completion." HOT 2
- Performing a sync on a configuration with Transparant Sync breaks stuff?? HOT 3
- DuplicateItemName exception HOT 2
- UnauthorizedAccessException with SyncSilent HOT 2
- When we are deploying the changes on the Sitecore DEV site by using Azure Paas we are getting this error HOT 1
- Unicorn RainbowCodeGeneration is not supporting Sitecore 10.2 for serializing model HOT 3
- Verb - Reserialize ERROR: The remote host closed the connection. The error code is 0x800704CD.
- Not possible to config patch the fieldFilter exclude list HOT 4
- Moved item can end up deleted on sync HOT 1
- Sync Challenge Issue
- Serialization issue in cloned items HOT 1
- *feature* Is Unicorn supporting Sitecore 10.3? HOT 3
- Moving items results in deleted items
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from unicorn.