topic Re: Deploying only perticular snapshot using ASR in Alfresco Archive

Deploying only perticular snapshot using ASR

kirit — Thu, 17 Dec 2009 13:21:03 GMT

HiIn alfresco 3.1, i need to deploy a snapshot by ASR to other server, but i dont want information of the previous snapshot to be deploy.Lets say i have 3 snapshots; s1(contains content c1,c2), s2(content c3,c4) and s3(content c5,c6) as s3 is latest.Now, so far we have not deployed any of these snap

Re: Deploying only perticular snapshot using ASR

mrogers — Thu, 17 Dec 2009 15:00:28 GMT

You can't prevent the full project from being deployed, and why would you want that. The snapshot is a consistent view of the entire project, not just the delta from the previous snapshot. Your use-case seems very strange, what are you trying to do?

You may be able to structure your project to exclude deploying certain parts of your web project, which is a more typical case.

Re: Deploying only perticular snapshot using ASR

kirit — Fri, 18 Dec 2009 03:52:11 GMT

Thank you mrogers,
Yes use case is little strange.
Let's say i am having a pre-prod server where users will add their contents and publish it, then my boss will have a look to those contents on site (front-end UI is in different portal not in alfresco) and then boss will like few of them but didn't like one or some issue with one content so we don't want to move that content while we do ASR. as that content may be created previously so it will also go once we deploy a latest snapshot which we don't what.

And as you have suggested to exclude some part of project, can you send me some links where i can refer how to achieve this?

I think i can put my requirement like this:
"I want to deploy a individual content only from one server to other server, not whole project"

Re: Deploying only perticular snapshot using ASR

mrogers — Fri, 18 Dec 2009 09:26:02 GMT

The "normal" way to do this is with a "review and approve" workflow. Your boss is a reviewer for each change and either approves or rejects. Should he approve the content goes into the staging sandbox which is then snapshotted and deployed. The point is that only approved content should be in the staging sandbox. And then you deploy a consistent view of the entire project.

One kludge to implement your requirement could be to have two folders in your pre-prod environment. "drafts" and "blessed". Upon "blessing" your boss moves the contents from "drafts" to "blessed". The final key in the puzzle is to add an "excludes" filter in the definition of the ASR to exclude everything in the "drafts" folder.