Baselines
Last updated
Last updated
A Baseline Child project is very similar to a Fork (forked repository) on GitHub where we create a clone of an existing project while maintaining a connection between the two projects. The connection exists between the Live environment of the existing project, the Baseline project, and the Development or Live environment - of the newly created project, the Child project.
Any project can act as a Baseline project.
The basic idea is that you have a project that contains all your standard Umbraco packages/components, maybe even configured with some default Document Types, which you want to use as a baseline for future projects. When you've made changes to your Baseline project, you can then push these changes out to all the Child projects with a click of a button.
To create a child project:
Log in to the Umbraco Cloud Portal.
Click the Create New Project button.
Select Baseline Project.
Open the Choose baseline drop-down list and select the Cloud project, the new project should be based on.
Choose either Starter, Standard or Professional plan from the Plan Selection window.
Enter the Project Name in the Project Information window.
Any Umbraco Cloud project can be used as a Baseline project
Choose an Owner from the drop-down list.
Enter your Name, Email, and Telephone in the Technical Contact section.
Click Continue.
Review the entered information and select I have read and agree to the terms and conditions and the Data Processing Agreement.
Click Create Project.
It might take couple of minutes for the project to spin up before your environments are ready. When your environments are ready, you will see a green light next to the environment name.
Depending on the size of the project you've chosen as a Baseline project, it might take several minutes before the Child project is ready.
When you've created the Child project you can choose to restore content from your Baseline project:
Go to the Content section.
Right-click the top of the Content tree in the Umbraco backoffice.
Choose Workspace Restore.
The Baseline project should already be selected as the environment to restore from
Click Restore from Baseline
If you do not see the content, Reload the content tree once the restore is complete.
As with any Git repository-based development, it is not uncommon to have merge conflicts as the repositories begin to differ. Read this article for more on the merge strategy we use and how to approach resolving these conflicts.
In this article, you'll find a guide on how to upgrade your Child project with changes from your Baseline project.
When you are working with Baseline Child projects you might sometimes want to have an individual configuration for each project - this can be handled using config transforms.
In this article, we will look at how to break the connection between the baseline and one of its child projects.
