Anyone have recommend settings they use for uSync? We've multiple developers working on doctypes which all need to be deployed. We're finding issues and not sure best how to handle them. I.e You run an import, and yet it still reports that there are things to import? or you run an import.. and it still shows that there are items to import, re-running the import then fails with duplicate key issues.. etc.

We don't have these problems. We use the default settings and in development configure uSync to import Everything at startup with no disabled handlers. In test/live we import Settings at startup with the content handler disabled. This means default + "export on save" which may not be default. Make sure you don't do any clean exports, and that you add alll uSync files to source control. The "still report that there are things to import" happens every now and then but it's always been a false flag... can't give a good example right now. For Settings I don't believe we've had any problems whatsoever, but for Content we would get the false flags, or even failures if entire root nodes are replaced etc.

We all work from sqllite but exlude these from source control. We then change the config files to do an unintended install, uSync then detects no content and does a full restore. This means that every new team member everything gets imported at first install. For everyone else once we're working on the project, they pull from source control and run a full import if needed and works great for us./

@Chad this has always happened to me, when i am pusing to development for example, manually. In this case i would remove the usync folder complelty and then add the new files and then sync. Sounds like its the same problem.

Clean exports or partial file check-in can cause you to have 'rouge' uSync files in the folder most deployment mechanisms don't remove files from the target by default, which is why we write the 'empty' files to disk when you delete, (so we can over write the existing ones). if those deletes are not captured and signed in or if you do a 'clean' export you loose them, and you can end up with the extra files. https://docs.jumoo.co.uk/usync/uSync/guides/importExport#caution-about-a-clean-export

Thanks Kevin, ok will be careful with that

We recently implemented husky.net in combination with usync. Via husky.net we detect if there are uSync changes. If there are changes we place the usync.once file so the import is triggered! This work really great and saves time during the startup process (depending of the amount of content this can save up to 10 seconds per build)!