First look at Sitecore XM Cloud: Part 2 - Intro to Sitecore XM Cloud Deploy

In this post, we will see how we can deploy our very first instance of Sitecore XM Cloud.

To get started with Sitecore Portal, please refer to part 1 of the series.

To get started, log into https://portal.sitecorecloud.io/ and click on "Managed My Projects". This will launch the Sitecore XM Deploy app.

Sitecore XM Cloud Deploy


Note that the Create New Project button is disabled as the partner account currently allows 2 projects. Ideally, this would be active is you are creating your first project.

Once you click on the "Create new project" button, you are presented with a 7 step wizard.

Step 0: Select an option
 
Select an option

 Step 1: Select a starter template

Select a starter template

Step 2: Project details

Project Details

Step 3: Deployment repository details

GitHub is the default option. More options coming soon.

Deployment repository details

Step 4: Template repository details

Template repository details

Click on "Create a new GitHub connection" and you are redirected to log into you GitHub account and pick a repository to map to the project. Once the connection is established you will see the following message:

Connection successful

Step 5: Deployment repository details

This step actually allows you to provide a name to instantiate a new repository that will be mapped to the project.

Deployment repository details

If you use the name of a repo that already exists you may see the following error:

Repo already exists

There seems to be glitch where even you provide a new name, you receive an error message that says " Main branch could not be located" or something to that effect. At that point, I just close the wizard and proceed to creating an environment manually.

You can delete a Project if you do not have any environments instantiated within it:
Delete project


In the Part 3, we will see how we can create an environment which actually contains the Sitecore XM Cloud instance.


Comments

Post a Comment

Popular posts from this blog

Is Rendered Item Valid XHtml Document Could not find schema information warnings during publish item Sitecore 7.2

Image
Note: Since we now live in the HTML5 world, the simple resolution to any XHtml validation errors is to remove the XHtml validation rules on  System->Settings->Validation Rules->Global Rules item. Sitecore should update it's validation rules to be relevant to HTML5. This make the rest of this post obsolete :). I created a simple approval workflow in Sitecore 7.5 and tried to approve an item for publishing and found a bunch of validation errors in the Validation Results. Most of them were related to the "Is Rendered Item Valid XHtml Document" section which looked like this: The problems were related to violations of the W3C HTML5 recommendation An important note here is: The element containing the character encoding declaration must be serialized completely within the first 1024 bytes of the document. Adding the following xmlns attribute to the Html tag fixed most of the errors: <html lang="en" xmlns="http://www.w3.org/1999/
Read more

Sitecore Tabbed Select Rendering dialog

Image
If you aren't already doing this, you should be! Found an interesting module (unable to find it on Sitecore Marketplace) to show renderings grouped into tabs while using the Select Rendering dialog from page editor. The idea is to go from this: To: The approach is promising with a few updates: Tried implementing it by inheriting from SelectRenderingForm and it did not work. No rendering items were being listed. Had to decompile Sitecore.Client.dll and copy the code from Sitecore.Shell.Applications.Dialogs.SelectRendering.SelectRenderingForm Had to comment the following line in OnLoad  this.Renderings.InnerHtml = this.RenderPreviews((IEnumerable<Item>)renderingOptions.Items); Found a few issues with the styles, could have be an updated style sheet for Sitecore 7.5, but had to add the following attributes to the tabstrip Background="white" Padding="0px" style="position:absolute; width:100%;top:0px" Here is a detailed description of my implementati
Read more

RESOLVED: Solr Exceptions - Document contains at least one immense term in field

If you implemented Solr with Sitecore using Solr 5.x, you may run into the following error when indexing extremely large content in string fields: org.apache.solr.common.SolrException: Exception writing document id <xxxuniqueid> to the index; possible analysis error. Caused by: java.lang.IllegalArgumentException: Document contains at least one immense term in field="<xxxfieldname>" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 9, 9, 10, 32, 32, 32, 32, 32, 32, 82, 84, 82, 83, 32, 70, 97, 99, 105, 108, 105, 116, 121, 32, 10, 32, 32, 32, 32, 84]...', original message: bytes can be at most 32766 in length; got <intgreaterthan32766> Caused by: org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got <intgreaterthan32766> This is due to the fa
Read more