Redeploy an entire site

[topherjohnson]

I'm a little confused as to how snapshots work. 

I'm using the Standalone Deployment engine.  Say in snapshot version 3 I have two files A and B, and I deploy it.  Then on my file system are A.xml and B.xml.  Then I create another file, C, and in version 4 I deploy it so on my file system I have A.xml, B.xml, and C.xml.

If I delete A.xml and B.xml on my file system (not in alfresco), how do I republish those files?  It seems like deploying a snapshot again, or reverting and deploying the reverted snapshot assumes that A.xml and B.xml are still on the filesystem, so it doesn't deploy them. 

The only way I've found to do it is to edit all the files again and submit them into a new revision and deploy that.  This method won't work once my file set grows.

In summary,  if I remove deployed files on my file system, in alfresco how do I redeploy all of my content to the filesystem.

[mrogers]

It's a known issue and (lowish priority) on my enhancements list.

What you can do is to delete the contents of the metadata dir on the standalone deployment receiver and then it will do a full deploy.  

But I'd like to know why you are fiddling around with the deployed content.     I've had several email conversations about "blended" deployments and indeed made several changes to support them.   What's your use-case?   Why are you deleting a.xml and b.xml?

[topherjohnson]

It's on a demo project, more of a curiosity than a dire requirement. 

Good to know though, thanks for the clarification / explanation.

[mrogers]

O.K.  thanks for your response.

So at the moment the only known use-case where re-deploy is needed is where an administrator or other program damages the content after its been deployed.   And for disaster recovery, there is the work-around above.    

I agree it needs to implemented at some point.     It's just not high priority.