Hey everyone, we're currently facing some issues with our current workflow. For local development we currently use a shared database for all developers. But this leads to issues with modelsbuilder when creating doctypes and so on. Now what would be the best approach for a local db? What db type would you use for local development. And what would be the best to keep these in sync when commiting changes? Using usync?

just a simple sqlite database could be fine

Thanks for your reply Ambert! Where could the paid version of usync then help me here?

the core uSync (the free bit) was built for this (multi-devs) - so if all the devs are working locally with local dbs, and checking in the changes they make to source control, usync will manage most (if not all) of the things for you. You will probibly want to turn off content syncing (https://docs.jumoo.co.uk/usync/uSync/guides/content) for devs, and depending on your own prefrences you might want to have Inport atStartup on https://docs.jumoo.co.uk/usync/uSync/reference/config#usyncsettings (so when someone checks out the code, starts up their site, everything is in sync). the paid version, comes into its own when you have editors (or devs) who want to push and pull things between sites without deployments, etc. So for example if your editors all work on the stage environment, and push things to live when they are ready. or if your not using a deployment pipeline (like azure - but really you should) - you can push doctypes, templates, etc between servers to get settings moved (but the free one does this if you deploy the files to the site and sync it).

Thank you a lot @Kevin Jump this really helped me out to understand it!

in my case we use a local db and (free) usync for updating settings and translations between environments, and also for content (test pages) but just locally, so you get a working website locally super quickly