I've been googleing around a fair bit trying to find a solution to this.
Basically, we need to put everything in source control except maybe content. masterpages, css, js etc are all easy. Document Types are not, neither are the settings for macro's.
The only option I can see is to manually export them (or make a package), unzip the package file and version that. Not exactly nice, but it'll work if people remember to do it.
However, I'd love a command line tool to do the package export and import - so we can maybe do it via Team City (CI tool). Anyone done this?
With regards to document types i do recall seeing something from Shannon and Slace they implemented action handler to export out xml of doc type on change and that was then being versioned cant see to find the post.
I've been working on a solution for this (doc type, macros, etc etc.), but work has put an end to this project lately.
A quick fix would be to export doc types (to xml) on the onchange event, and you could put up a filesystemwatcher to catch when a file was changed (put it in a folder where only the xml files of the doc types are located), and overwrite the xml of the doc type.
I guess you could do something quick for macros too.
The solution I've been working on involves a lot of UI work etc, so no chance of me finishing it in the near future.
Yeah, i can't remember the post either but essentially the idea is:
Bind to events in Umbraco to save out a serialized version of Document types, macros, dictionary, etc... which can then be saved to source control. Our Snapshot product (which will hopefully have a beta program launched soon) already does all of this serialization for you with the command line.
The tricky part is if you want to try to restore an umbraco instance based on this.... which we haven't written. The tricky part of this is that if you have references to exact node IDs in your config, pickers, etc.... doing a restore from data will create new ids.
Document Types (and other settings) in SVN
Hi there
I've been googleing around a fair bit trying to find a solution to this.
Basically, we need to put everything in source control except maybe content. masterpages, css, js etc are all easy. Document Types are not, neither are the settings for macro's.
The only option I can see is to manually export them (or make a package), unzip the package file and version that. Not exactly nice, but it'll work if people remember to do it.
However, I'd love a command line tool to do the package export and import - so we can maybe do it via Team City (CI tool). Anyone done this?
Thanks
N
Nic,
With regards to document types i do recall seeing something from Shannon and Slace they implemented action handler to export out xml of doc type on change and that was then being versioned cant see to find the post.
Regards
Ismail
Thanks Ismail, I'll have a hunt around - that sounds like a good idea - make a documenttype folder, and export to there on save.
Nice!
I've been working on a solution for this (doc type, macros, etc etc.), but work has put an end to this project lately.
A quick fix would be to export doc types (to xml) on the onchange event, and you could put up a filesystemwatcher to catch when a file was changed (put it in a folder where only the xml files of the doc types are located), and overwrite the xml of the doc type.
I guess you could do something quick for macros too.
The solution I've been working on involves a lot of UI work etc, so no chance of me finishing it in the near future.
Yeah, i can't remember the post either but essentially the idea is:
Bind to events in Umbraco to save out a serialized version of Document types, macros, dictionary, etc... which can then be saved to source control. Our Snapshot product (which will hopefully have a beta program launched soon) already does all of this serialization for you with the command line.
The tricky part is if you want to try to restore an umbraco instance based on this.... which we haven't written. The tricky part of this is that if you have references to exact node IDs in your config, pickers, etc.... doing a restore from data will create new ids.
I got that part working too!
Maybe I should release what I got, and instead of developing an UI, just hook it up with event handlers.
Here's the article Shan is referring to: http://farmcode.org/post/2010/06/11/Backing-up-Document-Types.aspx
Thanks everyone, thats a great help.
Cheers
Nic
is working on a reply...