Hi Jules, if you think to use usync is because you are working in a shared development environment with multiple instances of databases. Usync let you get all info on the database and maintain it on the website folder and then import it on another environment.
In fact I think the way to do this in a shared environment with source control is to have the following settings for all users that share the database:
<!-- run import at startup -->
<Import>false</Import>
<!-- export everything to disk at startup -->
<ExportAtStartup>false</ExportAtStartup>
<!-- when a user saves something, write it to disk -->
<ExportOnSave>true</ExportOnSave>
But when pushing to a separate database / environment you would have:
<!-- run import at startup -->
<Import>false</Import> <!-- J: This could be set to true if you want to have everything automated. I tend to want to do a manual import though -->
<!-- export everything to disk at startup -->
<ExportAtStartup>false</ExportAtStartup>
<!-- when a user saves something, write it to disk -->
<ExportOnSave>false</ExportOnSave>
uSync - Shared Umbraco Database
We have just installed uSync . We are using git for source control and persisting the uSync changes.
Until now we have been developing using a shared database.
My question is - should we use a shared database with uSync or should we now all have our own instances. Does it matter?
Julian
Hi Jules, if you think to use usync is because you are working in a shared development environment with multiple instances of databases. Usync let you get all info on the database and maintain it on the website folder and then import it on another environment.
In fact I think the way to do this in a shared environment with source control is to have the following settings for all users that share the database:
But when pushing to a separate database / environment you would have:
Quite simple in the end
Thanks
Jules
is working on a reply...