45

Updated with new information about NuGet feeds for 9.1 Previously, the 9.1 packages were in a separate feed, as of March 4th 2019, these have now been moved back into the main feed. The NoReferences packages are still removed. To avoid link rot, here are the feed urls for the official feeds: For all versions: NuGet V3 feed URL (Visual Studio 2015+) ...


20

We are using Zookeeper with Sitecore 8.1 Update 2, and as per the documentation here: https://zookeeper.apache.org/doc/r3.1.2/zookeeperAdmin.html we are using 3 instances. This is the minimum required. Three ZooKeeper servers is the minimum recommended size for an ensemble, and we also recommend that they run on separate machines. This works really well ...


14

We do our deployments as follows in our 8.1 environment using Team City, Octopus deploy and Unicorn (this is Simplified): a rewrite rule tells the load balancer to take CD1 out of the pool push the site NuGet packages to the CD and CM servers (we build this from Teamcity) deploy sitecore, the updated site code and serialised unicorn items to the CM sever ...


12

They are mostly self-explanatory, but here is the list of suffixes with the role names/descriptions: *.cm: Content management server *.cd: Content delivery server *.collection: The xConnect collection server, collects contact and interaction data *.identityserver: New in 9.1, this is the new Identity Server used for logging into the various other Sitecore ...


9

I would highly recommend that you watch the following presentation by Mike Edwards: Sitecore Nirvana - Continuous Deployment. It's about two sets of databases being replicated. It all comes down to process at the end. You can definitely work through and come up with a process which works for you and your environment. During deployments you would pause the ...


8

It comes down to support. Is there a known reason Sitecore wouldn't work on 2016? No. It will run on 2016 and in all likelihood there will not be any major issues in doing so. But if there is; this is what it comes down to. Let's say you ran into an issue and Sitecore Support was not able to help you out due to it being rooted in something around Server ...


7

The official Sitcore Nuget feed is hosted on myget.org as @Adam correctly points out the details are in that document. You can also read up more details about setting this up for your project in this blog post about the nuget feed but if you have an existing project that you want to migrate all references on, esp on a project which follows Helix guidelines ...


7

Yes you can call module from foundation layer. Please have a look here: https://helix.sitecore.net/principles/architecture-principles/layers.html for more details .


6

One strategy that has served me well is called Placeholder Fallback and was originally blogged by Charlie Turano at Hedgehog. In this strategy, you define your presentation on a parent item and it is inherited on all descendant items that contain a special fallback rendering. This avoids the issue of inheriting presentation from standard values across ...


6

In my attempt to follow the Helix design principles as closely as possible, the issue of Feature-to-Feature module references has come up quite a bit and still remains a bit fuzzy to me. According to the Helix Documentation, these types of references appear to be permitted in some cases, but are generally discoraged. A templates class should never ...


5

I haven't heard anything about Vision Stencils for Sitecore. But on an architecture visualization perspective I would recommend you to try Sitecore UML Tool. Its an architecture visualization tool helps visualize existing Sitecore architectures in UML and to create, visualize and deploy new Sitecore template architectures directly from their UML diagrams. It ...


5

If your only need is to keep the CD nodes only and you are okay with downtime on the CM, you can achieve 100% uptime of your CDs during deployments using a second publishing target. CD1 => Connected to Publishing Target 1 CD2 => Connected to Publishing Target 2 By swapping which CDs are in the Load Balancer you can take your time and control when you ...


5

You should start with a blank web application solution with no /sitecore files at all. If you need to add a file or modify a sitcore file, build the folder structure in your project so on deployment, it will overwrite the existing sitecore file. All Sitecore config changes should be in the solution, in a /App_Confif/Include/z_[Client] folder. All your dlls ...


4

I think that the best practice is not to store Sitecore in your source control. So your source control should contain only files that are relative to your solution and on build process you deliver your codebase and files to Sitecore instance directory which is not part of your source control. So from my point of view: do not store sitecore files do not ...


4

Without SXA I would build this as a single feature with 4 components, all based off the same data template. Create a template that contains all the fields you require. Lets call it ImageCallout Create 4 renderings that have the razor setup to the 4 different styles that you have specified. They should all use your ImageCallout template as the datasource for ...


4

We have always used database-level replication to keep core databases in sync. I don't have experience doing this with publishing, but I have a couple concerns. These are things that happen when an item is published that you may not want for core databases: You will lose version history of the items on the destination core database since publishing only ...


4

After hours of investigating the issue, I found the problem that I am supposed to send the load command using ClientResponse instead of SendMessage. Thanks, everyone for your help. string load = $"item:load(id={workflowItem.ID},language={workflowItem.Language},version={workflowItem.Version})"; Context.ClientPage.ClientResponse.Timer(load, 2);


4

It sounds like your Listing component does not belong in the Articles module, if it needs to display more than just Article items. Similar to how you would implement a Navigation component, the Listing component should have an associated interface template (e.g. _ListingItem) which defines the field(s) needed for the Listing. This interface template can be ...


3

You have more options and they depends mainly on the requirements Option 1 You can have all fields in 1 template and then depends on the filled fields in preview and normal mode which should be shown, but you show all as editable in Experience Editor. This is a good solution if you want editors to able to change the content dynamicly and you want to use ...


3

Sitecore jobs is the best option in such case, but you can use them in different ways. Best approach for using them may vary by business requirements, like frequency of user logins and the time frame in which you want to update profiles. Below are some approaches - Once the user is logged in, create a job to update that user's profile data. In case ...


3

If you consider the basics of the Helix principles that features should not be aware of the project layer, you could decide that the "Header" feature you are developing should have 2 sets of contoller-model-view. In my opinion, a feature can have multiple implementations of something that might seem similar. If in your case the header is so different between ...


3

Start by reading the Sitecore Helix Documentation. The component-based architecture it describes is definitely the way to go. Most of the accelerators use something like it even if they don't use the Foundation-Feature-Project layers. Most of the accelerators also move presentation details away from the template standard values to some extent. SXA has ...


3

This question is quite broad as there are many aspects to it. Here is my perspective of this subject. should you add Sitecore files to source control? Only those that are needed for the build to run and that may be changed as part of the development of your website. For example you may want to add Sitecore dlls because they are referenced so if you are ...


3

If you have two CD servers behind LB, you can switch OFF 1st CD, clone databases and update content change connection strings on 1st CD update code of 1st CD switch ON 1st CD, Later you can repeat that procedure for 2nd CD (skip step with databases, you will just switch connections strings as you already have dbs with new contnent used by 1st CD)


3

Two Modules should be split into different structures in your foundation layer. However they can definitely reference each other. http://helix.sitecore.net/principles/architecture-principles/layers.html#foundation-layer Unlike the Feature layer, there is no strict convention on dependencies between modules in the Foundation layer. This means that ...


3

Is it possible? Sure, anything is possible. The question you need to ask is how much removal of configurations do you want to deal with, and possible break the ability to upgrade in the future? Is it advisable? That's pretty opinionated, which might result in the closure of this question. However, before it's closed, let me offer this professinal's ...


2

Although this post was asked a year ago, I guess it's still worth to comment as every project has it's own flavor of deployment. This is what we do in our latest project whenever we want to deployment the hotfixes/change requests to Content Deliveries (CD) without downtime, as follow in order. Environments: PROD - Production Environment (Active) : ...


2

The best approach to this will require some data grooming. At its simplest, it can be done with nothing besides stock Sitecore and the Sitecore Powershell module. If you're not comfortable with Powershell, or you need to take a more iterative approach, you could also write code to handle your transformation. I like to park pages in /sitecore/admin for just ...


2

Sitecore 8.2 Update 3 does support Windows Server 2016. https://kb.sitecore.net/articles/087164 In the operation systems table, Windows Server 2016 is checked under 8.2 and links to the following note: "[21] Compatible beginning with Sitecore XP 8.2 Update-3."


2

Sitecore provides some guidance for Azure based on topology which can be found here https://kb.sitecore.net/articles/043375 Jarmo is correct that there are many factors to take into consideration and these numbers will not be accurate for every Sitecore solution. If you are not using Azure you might want to compare this to similar hardware on your platform.


Only top voted, non community-wiki answers of a minimum length are eligible