My company has assigned two developers to create a new website with Umbraco. We each have independent dev environments with VS2019 and SQL. Our code is stored in a shared git repo.
How do we merge database changes from one developer to another developer?
And how do we deploy database changes to our production server?
We use the Converge package, it has proved invaluable. It has a few quirks and needs to be merged in a certain order, there is a post explaining in the Converge forum. Stuart the developer is very helpful.
Our developers use a shared database in SQL server so we just need to merge with the production server
You can use uSync for syncing the settings (and content if you want*) between your developer's sites.
uSync will write all settings, and changes from the database to disk - so when ever you update a doctype, datatype, template ect a config file is written to the uSync folder
you can then check the uSync folder into the git repo. and when the developers check out the changes they can import them into their build. so all the settings will stay in sync on their local installs.
uSync will also work with your deployment processes so you can have the changes imported from disk when you deploy your site. So for example you site builds from your repo and uSync can import changes from disk as the site starts up.
uSync does the settings and uSync.Content edition does the content bits.
Merging database changes to production
My company has assigned two developers to create a new website with Umbraco. We each have independent dev environments with VS2019 and SQL. Our code is stored in a shared git repo.
Hi Peter
We use the Converge package, it has proved invaluable. It has a few quirks and needs to be merged in a certain order, there is a post explaining in the Converge forum. Stuart the developer is very helpful.
Our developers use a shared database in SQL server so we just need to merge with the production server
Link to post about order of synching stuff
Converge 8
Hi,
You can use uSync for syncing the settings (and content if you want*) between your developer's sites.
uSync will write all settings, and changes from the database to disk - so when ever you update a doctype, datatype, template ect a config file is written to the uSync folder
you can then check the uSync folder into the git repo. and when the developers check out the changes they can import them into their build. so all the settings will stay in sync on their local installs.
uSync will also work with your deployment processes so you can have the changes imported from disk when you deploy your site. So for example you site builds from your repo and uSync can import changes from disk as the site starts up.
uSync does the settings and uSync.Content edition does the content bits.
is working on a reply...