I have previously introduced the procedure for creating a new project and launching a new CMS. This time, we would like to create a development branch in the same GitHub repository and launch an instance using the code under development.
![](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2FvTmzjALP8BBJUfw2Bjcim%2F033eadf6bd0107c905c07e0214c4e4dd%2Fengin-akyurt-gJILnne_HFg-unsplash.jpg&w=3840&q=75)
Adding an Environment with XM Cloud
Assume that the current project has one environment available.
![add-nonpro01.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F4onpa2io6Cf0HPh281zVd7%2F1451524b90e4d4553ea0147572eb4264%2Fadd-nonpro01.png&w=3840&q=75)
Click Create environment. Enter the necessary items for the environment you wish to add. In this case, the following settings were made.
![add-nonpro02.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F6pdvFy7FemqFvLObQrvWd7%2Fdfbc3986cfc2c173ac0cf8a40f9b5021%2Fadd-nonpro02.png&w=3840&q=75)
The development branch is in the following state
- Tailwind CSS style sheet is applied to Next.js
- Information about the Site is serialized and stored.
This assumes that the development environment has the site in an added form and is capable of using Tailwind CSS.
After a while, the CMS starts up, and when you access the dashboard, you will see the following
![add-nonpro03.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F4A7Bhi4c6v43XroxsjlZYn%2F5d9850e5f51cff66f20237a3b2562de9%2Fadd-nonpro03.png&w=3840&q=75)
After successfully importing the serialized data contained in the repository, the CMS is now up and running with the site added.
Summary
In this case, we checked how the serialization data is activated when it is included when adding an environment. Serialization data is only imported when creating a new environment with XM Cloud Deploy, not when running Redeploy on an already deployed CMS.