I've been working with an organization that have a number of companies which are using EPiServer sites. All sites have different licenses but share database.
When deploying all sites restart at the same time (because the sites are sharing code base and publish folder) so we will now separate the files the the sites so they lie in separate folders.
To deploy one site at the time takes longer but doesnt impact all sites when deploy is made.
So far so good.
But what if a change in a page type (PTB) is made when on site is deployed and this changes the database - isn't there a risk for a miss-match on the other sites?
I've been working with an organization that have a number of companies which are using EPiServer sites.
All sites have different licenses but share database.
When deploying all sites restart at the same time (because the sites are sharing code base and publish folder) so we will now separate the files the the sites so they lie in separate folders.
To deploy one site at the time takes longer but doesnt impact all sites when deploy is made.
So far so good.
But what if a change in a page type (PTB) is made when on site is deployed and this changes the database - isn't there a risk for a miss-match on the other sites?
Is there a best practice for this?
Best regards,
Jonas