I use the very popular uSync package. It's not code first (I don't think there is a code first solution for v8) but uSync is excellent for promoting changes in doc types, data types and so forth between your environments.
We have been building something internally, for code first specific..
For the other, uSync and later umbraco deploy, are great options. Another one is to create packageS on your development sites, from your doctypes / content, and install them to the target environment.
hi - thanks for the uSync suggestions. Ideally we're looking for a code-first option in umbraco 8 so that we can continue to promote datatype, doctype, template, and sometimes content changes automatically with our deployment packages.
uSync if you want to kind of get things like migrations and source control with non code assets. In v8 and v7 there is no code first. There used to be in v6 uSiteBuilder which was like a clone of Episerver PageBuilder however it had its issues.
Way I see it code first is for controlling effectively via migrations your non code assets and to give you strongly typed models.
With usync you get source control of non code assets and with models builder you get strongly typed models (with some caveats, namely its tied in with IPublishedContent although you code use ditto with will give you pure models).
Interested to know what uSync doesn't do/work for you ? If there is something you think it should do (or explain better!), feel free to drop an issue in the repo and we will be more than happy to take a look.
code-first in umbraco 8
hello - what is everyone using / planning to use for a code-first approach in umbraco 8? (i.e. for promoting cms changes from dev to test, live)
thanks
I use the very popular uSync package. It's not code first (I don't think there is a code first solution for v8) but uSync is excellent for promoting changes in doc types, data types and so forth between your environments.
Regards, Magnus
We have been building something internally, for code first specific..
For the other, uSync and later umbraco deploy, are great options. Another one is to create packageS on your development sites, from your doctypes / content, and install them to the target environment.
hi - thanks for the uSync suggestions. Ideally we're looking for a code-first option in umbraco 8 so that we can continue to promote datatype, doctype, template, and sometimes content changes automatically with our deployment packages.
set
importto truehttps://usync.readthedocs.io/backoffice-config/ :)
hello - so does anyone using anything other than usync? thanks
Andrew,
uSync if you want to kind of get things like migrations and source control with non code assets. In v8 and v7 there is no code first. There used to be in v6 uSiteBuilder which was like a clone of Episerver PageBuilder however it had its issues.
Way I see it code first is for controlling effectively via migrations your non code assets and to give you strongly typed models.
With usync you get source control of non code assets and with models builder you get strongly typed models (with some caveats, namely its tied in with IPublishedContent although you code use ditto with will give you pure models).
When its comes to Umbraco I have 2 mottos:
;-}
Regards
Ismail
Hi Andrew,
Interested to know what uSync doesn't do/work for you ? If there is something you think it should do (or explain better!), feel free to drop an issue in the repo and we will be more than happy to take a look.
Kevin
is working on a reply...