I'm wondering if there's something i'm not seeing, or if there's another external solution for this: for documents, there's built in version history and rollback, so as Im making changes to my site, I can easily just move back to a previous version if i mess up, allowing me to just hack away from the web UI.
However, for CSS, Templates and XSLT, there's nothing like that. What are my options here, short of keeping copies of everything in an external source control system?
For development work, most developers who use Umbraco do use a source-control system to version their files (e.g. css, scripts, usercontrols, xslt, etc).
What are your concerns about using a source-control system?
No concern per say, it just forces developing on a local install, which feels a little overkill when I only have a few XSLTs and templates that could very well just be edited straight in the editor, but no revision control built in kinds of stop that flat :)
Its not a big deal, its just, I was about to do just that when i noticed the documents had built in revision mechanism. I was like "cool! I can use that for my XSLTs and templates!", then peeked there and booooo, its only on documents. Its no show stopper, it would simply have been a nice convenience to not have to resort to an external source control for a small scale project that doesn't require any .NET development.
Lee is right, there is nothing built in, and the majority of developer just use regular source control, but you could look at writing something to do the backups for you, as Umbraco fires many events. Checkout this article from the guys at the Farm for an example of automatically backing up doc types, there is no reason this couldn't be extended.
Versions for non-document assets
Hi,
I'm wondering if there's something i'm not seeing, or if there's another external solution for this: for documents, there's built in version history and rollback, so as Im making changes to my site, I can easily just move back to a previous version if i mess up, allowing me to just hack away from the web UI.
However, for CSS, Templates and XSLT, there's nothing like that. What are my options here, short of keeping copies of everything in an external source control system?
Thanks!
-Francois
Hi Francois, welcome to Umbraco!
For development work, most developers who use Umbraco do use a source-control system to version their files (e.g. css, scripts, usercontrols, xslt, etc).
What are your concerns about using a source-control system?
Cheers, Lee.
No concern per say, it just forces developing on a local install, which feels a little overkill when I only have a few XSLTs and templates that could very well just be edited straight in the editor, but no revision control built in kinds of stop that flat :)
Its not a big deal, its just, I was about to do just that when i noticed the documents had built in revision mechanism. I was like "cool! I can use that for my XSLTs and templates!", then peeked there and booooo, its only on documents. Its no show stopper, it would simply have been a nice convenience to not have to resort to an external source control for a small scale project that doesn't require any .NET development.
Thanks!
Hi Francois,
Sorry afraid there's nothing built-in to Umbraco for versioning the 'static' files.
My suggestion is make regular back-ups.
Cheers, Lee.
Hey Francois,
Lee is right, there is nothing built in, and the majority of developer just use regular source control, but you could look at writing something to do the backups for you, as Umbraco fires many events. Checkout this article from the guys at the Farm for an example of automatically backing up doc types, there is no reason this couldn't be extended.
http://www.farmcode.org/post/2010/06/11/Backing-up-Document-Types.aspx
Matt
Thanks, that clear things up :)
-Francois
is working on a reply...