uSync / uSync.ContentEdition - will always be free.
Complete elements will have a licence - we are working out what the paid version will look like, currently, we are heading towards. some sort of 'pipeline/project' licence (so one licence covers all devs/servers for one project. (might give you a shout to chat about this, as we are canvassing opinions)
Events
Good question I think they do :) to be honest i haven't checked, all the events are in uSync and we are using the core in all the products so they should be firing - we will go check.
Custom Properties
Yes - we are probibly going to some examples in uSync.Community.Contrib project but you can see how we have done this for the grid / nested content in the source. Content Mappers
Dependencies
Yes, if you have those options on, it will find dependencies for doctypes, datatypes, templates, macros, and media items that any content may contain.
The setup is flexible enough that you can go from
"*I am syncing all my settings I don't need them as part of a publish" *
to
"Nothing is in sync, when i publish work it all out"
as such one of our tests is publish from a built site to a completly blank one and make sure all the bits get deployed.
its down to which of the options you configure for each server when you set them up.
having the uSync files checked in won't affect publisher, it doesn't use those files.
but you might still want them for source control / basic setup, and you might choose to still deploy settings via CI/CD and the standard files. only using publisher for content/media
'pipeline/project' licence (so one licence covers all devs/servers for one project
So for client x i have say dev /staging and live. Once licence feed would cover all three instances?
Or you thinking a license per environment? Also how much are you thinking? We are about to start project soon going live January and usync.publisher is perfect fit for this, so no rush to release and come up with pricing model
Yeah, the idea is that would be one licence and we think we know how to do that ;)
it will probably be a domain thing - so on a purchase, you specify the live and stage domains and we licence for them (and sub-domains, v similar to Translation Manager).
Price is in the works. we are canvasing option, I think i will drop you a line to chat :)
Things I am unsure of
I am going to start play with this very soon.
Basically we have v8 site and do not have umbraco deploy will be ready for go live so was potentially looking at this as alternative.
Few questions:
Regards
Ismail
Hi,
Happy to answer.
Licencing
uSync / uSync.ContentEdition - will always be free.
Complete elements will have a licence - we are working out what the paid version will look like, currently, we are heading towards. some sort of 'pipeline/project' licence (so one licence covers all devs/servers for one project. (might give you a shout to chat about this, as we are canvassing opinions)
Events Good question I think they do :) to be honest i haven't checked, all the events are in uSync and we are using the core in all the products so they should be firing - we will go check.
Custom Properties Yes - we are probibly going to some examples in uSync.Community.Contrib project but you can see how we have done this for the grid / nested content in the source. Content Mappers
Dependencies
Yes, if you have those options on, it will find dependencies for doctypes, datatypes, templates, macros, and media items that any content may contain.
The setup is flexible enough that you can go from
"*I am syncing all my settings I don't need them as part of a publish" *
to
"Nothing is in sync, when i publish work it all out"
as such one of our tests is publish from a built site to a completly blank one and make sure all the bits get deployed.
its down to which of the options you configure for each server when you set them up.
Kevin,
Cool. One more thing, when using this can we do away with usync defintion files being checked into source?
yeah - you can choose. :)
having the uSync files checked in won't affect publisher, it doesn't use those files.
but you might still want them for source control / basic setup, and you might choose to still deploy settings via CI/CD and the standard files. only using publisher for content/media
its pick and mix really.
Kevin,
Awesome will have a play and report back.
Kevin,
So for client x i have say dev /staging and live. Once licence feed would cover all three instances?
Or you thinking a license per environment? Also how much are you thinking? We are about to start project soon going live January and usync.publisher is perfect fit for this, so no rush to release and come up with pricing model
;-}
Ismail
Hi
Yeah, the idea is that would be one licence and we think we know how to do that ;)
it will probably be a domain thing - so on a purchase, you specify the live and stage domains and we licence for them (and sub-domains, v similar to Translation Manager).
Price is in the works. we are canvasing option, I think i will drop you a line to chat :)
Kevin
is working on a reply...