Festina Lente
Last year, I wrote the Sitecore XM to XM Cloud Content Migration article about the brand-new tool from Sitecore that helps to migrate content, media and users to XM Cloud. Now, I would like to share what is new in the just-released XM to XM Cloud Tool v2.1.
Sitecore has lots of customers who developed their solution based on classic Sitecore OnPrem which exists in the market for 2 decades. Also, Sitecore released the XM Cloud, a fully SaaS solution in July 2022.
Lots of customers continue to use the OnPrem solutions, new customers prefer to use the SaaS version and of course, some would like to switch to it, but it requires lots of effort. Sitecore just released to the public a brand-new XM to XM Cloud Content Migration tool that assists in minimizing the account’s barriers to migrating to Composable DXP.
It helps migrate customers’ data from the source of the XM OnPrem instance to the XM Cloud account. It migrates the content, media, and internal users (but not custom site data at this moment).
Continue reading “Sitecore XM to XM Cloud Content Migration”The Sitecore Order Cloud is a rich and mature e-commerce engine.
It has a few must-know security related definitions:
There are 2 types of system requirements:
The Locust is an alternate tool to the JMeter. Locust allow you to write load tests in python, this tutorial describes how from scratch make a simple load testing and see results. Let’s do the following steps:
Please pay attention to the output url: http://0.0.0.0:8089, please adjust the address to the next: http://localhost:8089, (as the IP-format may not work) and paste to the browser, you should see the next:
Continue reading “Locust as a modern load testing framework”1. Copy a file from the App_Data/logs/ path of the default/cm-5c57dbd5d5-pqwh9 pod into the local C:/myf/log.txt file:
kubectl cp default/cm-5c57dbd5d5-pqwh9:App_Data/logs/log.20201215.092051.txt /myf/log.txt
2. Copy the Sitecore.ContentTesting.dll file from the local machine into the pod with path bin/Sitecore.ContentTesting.dll
kubectl cp C:\Work\Solutions\CT\code\Sitecore.ContentTesting\bin\Debug\Sitecore.ContentTesting.dll default/cm-5c57dbd5d5-pqwh9:.\bin\Sitecore.ContentTesting.dll
3. Copy all the files from the App_Data/logs/ path into the local C:/myf/:
kubectl cp default/cm-5c57dbd5d5-pqwh9:App_Data/logs/ /myf/
Note for the #3: please check that all the files are copied, in my case some of them were missed somehow, if you know why it may happens please let me know, thank you in advance!
Let’s say we have a simple smart contract MemoryToken, it can be even a stub which has only 1 field name.
pragma solidity ^0.5.0;
contract MemoryToken {
string public name = "Memory token";
}
This post is to show how similar every technology to each other. If you experienced with NUnit, XUnit, Jasmine, Protractor, etc., you can easily figure out how to write unit-tests for blockchain smart-contracts using the Truffle tool which under the hood is NodeJS.
Continue reading “Unit-tests for blockchain smart contracts with Truffle”The Netlify service allows you not only to deploy Jamstack apps, but also do split testing, meaning that can show to users different variations of the same page. The approach they provide is quite interesting and different from common software practices. I would say it’s even more related to configuration.
Let’s say we have simple JAMstack website. To use the split-testing approach we should have the source code in Bitbucket, Github or Gitlab. Make sure your latest changes is in the master branch.
Then login to the Netlify account, go to the Team overview tab and click the New site from Git.
Then do 3 simple steps which take less than a minute and you should have connected repository to the Netlify.
Continue reading “Netlify Split Testing”
For the last few days I’ve noticed weird behavior in Sitecore instances which are related to Solr, for example:
For all of this things I haven’t pay much attention to start troubleshooting, because I’m working in another area which not related to indexes, the behaviour is quite new for me and just simple reboot has helped.
Ivan's Blog 