New Deployment for existing project
I have a client who has already built a project with a channel-type website on the Kentico administration page (CMS). Let's call this Project A. Currently, I have created a new project, Project B, with a channel type of Headless. I attempted to create a deployment package to publish it to the QA environment. After publishing, I checked the CMS and noticed that the headless channel was created successfully. However, the existing channel (Project A) seems to have been replaced by the new one. As a result, I can no longer preview the existing pages on the QA CMS.
When I created Project B, I followed the instructions from scratch using the first installation guide. I used the kentico-xperience-mvc template. My question is: How can I publish Project B to the portal without replacing the existing project (Project A)?
I followed the instructions in the Deploy to SaaS guide to create the deployment package. I'm using the same salt hash from the portal when i created Project B
Environment
- Xperience by Kentico version: [30.1.3]
- .NET version: [8]
- Execution environment: [SaaS]
Answers
Let me check if I understand correctly. You have two XbyK projects and one SaaS environment, correct?
A single SaaS environment is designed to run only one project at a time, as it has reserved resources and domain names for a single project. You have the following options:
- Request an additional SaaS environment from Kentico.
- Host Project B outside Kentico’s SaaS platform.
- Set up a Headless channel in Project A to manage both channels within a single project and SaaS environment.
In any case, I recommend checking with a Kentico representative.
Technically, yes, there are two XbyK projects and one SaaS environment. However, I do not have the source code for Project A. As a result, I created Project B from scratch. Unfortunately, I had already set up a headless channel, headless items, uploaded media libraries, created content types, and added content, all of which are stored in the local database.
My goal aligns with option 3 that you provided. Is there a way to upload a deployment package without replacing Project A (Channel Type: Website), given that I don’t have the source code for Project A? Additionally, I want to ensure that the data on my local environment is also published to the QA SaaS environment.
If you don't have access to the source of Project A, option 3 will be locked for you.
To my knowledge, it's not possible to have two projects deployed within a single SaaS environment. When you upload a new deployment package, its content is deployed and replaces the previous deployment.
Regarding promoting your local data to a SaaS environment, you need to ensure that the required objects are serialized through the $CDRepository/repository.config file. I wrote a blog post about SaaS deployments where you can find more details.
To answer this question, you have to login first.