Importing items using Sitecore CLI
Previously, we added the Next.js template to the project, but at this stage Sitecore has no data, so we get an error. Therefore, we would like to import the sample data using Sitecore CLI.
You can check blog articles order by publish date.
Previously, we added the Next.js template to the project, but at this stage Sitecore has no data, so we get an error. Therefore, we would like to import the sample data using Sitecore CLI.
The environment we've set up in four parts lacks a Next.js project. We'll add a sample site by integrating the code into the project. This process will be introduced in two steps. In this session, we'll get the Next.js sample running.
After setting up the container environment, the admin interface is still in English. This time, we'll introduce the process to switch it to Japanese. We'll demonstrate how to deploy resources by copying files when creating the Docker image.
To align the container environment with the server, we'll ensure all necessary modules are available in Docker. The current Docker container already has SXA and Horizon configured, so we'll install any missing components as needed.
Previously, we set up the server, but the key is to run the container locally. Let's organize the steps we've taken so far to prepare an environment where Docker-based Sitecore can run on our local machine.
I haven't posted on my blog for about a month, as I've been working on a new series to summarize previous tips. In this series, we'll build an environment to run Sitecore Headless locally, reflect changes on the server, and deploy it to a web server.
We have introduced the procedure for deploying Sitecore on the Azure Kubernetes Service. This time, we will check the procedure for setting up an environment that enables the same process on macOS.
We have introduced Sitecore on Azure Kubernetes Service in two parts as a preparation for deploying Sitecore on Azure Kubernetes Service. This time, we are ready to deploy Sitecore on Azure.
Regarding the setup procedure for deploying Sitecore using AKS, we will now create the data in the various configuration files. The data in the configuration files will be used as the data for the actual deployment.
Docker is a convenient mechanism for running Sitecore at hand, but when it comes to using containers for operations, it is more convenient to use Azure Kubernetes. Kubernetes is a convenient way to deploy containers.
We've covered how to run Sitecore in Docker containers locally. However, these steps differ from those for deploying to cloud services. For actual operations, Sitecore is combined with Azure Kubernetes Service (AKS).
The CI HUB supports Adobe Creative Cloud, Microsoft Office, and other tools that you may use on a daily basis. In this article, we will introduce the integration with Figma, a design tool.