you can control this just by what folders you choose to copy between sites (so copy all but /data/content /data/media to live and only copy those folders back from live)
but if you want to/can only have the whole usync folder copied between sites I would suggest you use Hander Groups within the usyncbackoffice.config (see http://usync.readthedocs.io/handler-config/)
With that you can setup the handlers to do what you need, (see below) and then the only diffrence between live and production will be the group value.
(all the below settings are in /config/usyncbackoffice.config and would probibly need some tweaking to your exact needs. )
This handler group would enable all the config stuff but only enable the saving of things to disk for Content and Media (meaning they never get imported).
I wouldn't turn off the actual import of config on dev, because you will want that for source control (so you might have multiple devs making changes, you will want that to be reflected on all developers pcs.
I have worked with other CMS systems before, but I have to say the Umbraco ecosystem, the community and the developer experience are next to none, AFAIC.
Request configuration for only importing content from Production to Development machine
Could you please suggest a configuration that will enable the following scenario:
Thank you
Umbraco 7.6.6, uSync.BackOffice 4.0.0.760, uSync.Core 6.0.0.760, uSync.Content: 4.0.0.760
Hello,
you can control this just by what folders you choose to copy between sites (so copy all but /data/content /data/media to live and only copy those folders back from live)
but if you want to/can only have the whole usync folder copied between sites I would suggest you use Hander Groups within the usyncbackoffice.config (see http://usync.readthedocs.io/handler-config/)
With that you can setup the handlers to do what you need, (see below) and then the only diffrence between live and production will be the group value.
(all the below settings are in
/config/usyncbackoffice.config
and would probibly need some tweaking to your exact needs. )Import Dev Changes to Live (but not content).
This handler group would enable all the config stuff but only enable the saving of things to disk for Content and Media (meaning they never get imported).
*import just the content (live to dev) *
then on live
and dev
I wouldn't turn off the actual import of config on dev, because you will want that for source control (so you might have multiple devs making changes, you will want that to be reflected on all developers pcs.
Worked like a charm!
I have worked with other CMS systems before, but I have to say the Umbraco ecosystem, the community and the developer experience are next to none, AFAIC.
Thank you.
is working on a reply...