CD Repository

2025/10/03 6:54 AM

I'm using a local dev version of xbyk and a local database. Then I push edits to GitHub and use GitHub Actions to push everything to staging on Azure. I followed the instructions and created a CD repository. But when I create a new pagetype, nothing is written to this repository. What could be the problem?

Tags:
CI/CD Deployments

Answers

2025/10/03 7:45 PM

The CD repository, unlike the CI repository, is not automatically kept up to date. It has to be re-generated (somewhere) and deployed with the application code.

You can generate it locally and commit the entire repository to source control or you can generate it externally, like in a CI/CD pipeline, so that it doesn't create a lot of noise in your Git history. The Kentico Community Portal generates the CD repository in a GitHub workflow using a backup of the database and the CI repository (which is committed to the Git repo).

Check out the blog post Xperience by Kentico CI/CD developer scenarios for more details.

If you are interested in what that repository.config file might look like for the CD repository, take a look at the Kentico Community Portal source code for an example.

Then, you deploy the application (along with the CD repository) to your target environment and update the database with the schema and content changes described by the CD repository.

To do this you use the --kxp-cd-restore command. It's described in our documentation.

To response this discussion, you have to login first.