uSync takes all the umbraco bits and stores them on disk - uSync doesn't store any of its own settings or data in the DB (unless you are using snapshots - which stores snapshot ids in the db).
so for usync everything is on the disk, as steve says in /usync/data by default .
and the history info (shown on the history tab) is stored in /app_data/temp/usync -
are you looking for anything specific in the data ?
Is there a write-up on how uSync communicates with Umbraco?
As I am wondering, since we do don't allow our content editors in production to do any changes to backend stuff like DataTypes, DocTypes, macros, mediaTypes and/or Templates, do I need to deploy uSync folder at all to production? As in dev, when I make a change, doesn't the change go to the database?
but if you want to get changes from dev to live then if they are not sharing a database you should be copying the usync folder up (but read the posts on this - you might for instance want to turn of automatic updating and do some of this via the dashboard)
I only have one database but two servers in Umbraco's "Flexible Load Balancer" configuration. If let's say I add a edit an existing doctype to my dev env or add/delete same and check it in my Visual Studio 2017 solution, at this point doesn't uSync push my changes to the database? And if I deploy my database changes to production, I should be all set and not
Umbraco Tables related to uSync
We are on Umbraco 7.11.1. For my own education, does anyone know what table(s) hold the information in the uSync folder?
If so, can you tell me which tables they are?
Thanks
Tom
Isn't everything stored in the /usync/data/ folder itself?
No everything in uSync should have a record in the database too.
Hi Tom,
uSync takes all the umbraco bits and stores them on disk - uSync doesn't store any of its own settings or data in the DB (unless you are using snapshots - which stores snapshot ids in the db).
so for usync everything is on the disk, as steve says in /usync/data by default .
and the history info (shown on the history tab) is stored in /app_data/temp/usync -
are you looking for anything specific in the data ?
Kevin
Kevin:
Is there a write-up on how uSync communicates with Umbraco?
As I am wondering, since we do don't allow our content editors in production to do any changes to backend stuff like DataTypes, DocTypes, macros, mediaTypes and/or Templates, do I need to deploy uSync folder at all to production? As in dev, when I make a change, doesn't the change go to the database?
Thanks Kevin.
Tom
Hi Tom,
I've used uSync for over a year and I really love it, but for your own sanity and your client's (if you have) NEVER use uSync in production.
It doesn't clean up after itself and it WILL mess your production up unexpectedly. use it up to staging and then remove it.
Cheers
Harry
Hi Tom,
it sort of depends on how you deploy to live.
(some discussion of that here https://blog.jumoo.co.uk/2017/working-with-usync/)
also : https://usync.readthedocs.io/
but if you want to get changes from dev to live then if they are not sharing a database you should be copying the usync folder up (but read the posts on this - you might for instance want to turn of automatic updating and do some of this via the dashboard)
Kevin:
I only have one database but two servers in Umbraco's "Flexible Load Balancer" configuration. If let's say I add a edit an existing doctype to my dev env or add/delete same and check it in my Visual Studio 2017 solution, at this point doesn't uSync push my changes to the database? And if I deploy my database changes to production, I should be all set and not
and not have to deploy the uSync folder or files, right?
is working on a reply...