I was under the impression that Courier takes care of sorting out the database based on revisions stored on disk so that changes to the backoffice items like Document Types, Templates, Data Types, Member Types and so on can be automatically managed with source control, like git.
But after a few commits, I want to go back and start from an earlier point. So I reset to the earlier commit (Umbraco.Web project) and go to run it, but get all kinds of errors because the Data Types added in newer commits are still showing up in the Backoffice tree, but clicking on those nodes generates an error.
So I think the database still has references to the new elements, but I thought that Courier is meant to update the database.
Is that what Courier is meant to do? Is there a way to regenerate the database when checking out a different commit? Am I doing it wrong?
Checking out previous commit but newer Umbraco backoffice elements remain in database.
Hi,
I'm building an Umbraco Cloud project.
I was under the impression that Courier takes care of sorting out the database based on revisions stored on disk so that changes to the backoffice items like Document Types, Templates, Data Types, Member Types and so on can be automatically managed with source control, like git.
But after a few commits, I want to go back and start from an earlier point. So I reset to the earlier commit (Umbraco.Web project) and go to run it, but get all kinds of errors because the Data Types added in newer commits are still showing up in the Backoffice tree, but clicking on those nodes generates an error.
So I think the database still has references to the new elements, but I thought that Courier is meant to update the database.
Is that what Courier is meant to do? Is there a way to regenerate the database when checking out a different commit? Am I doing it wrong?
is working on a reply...