Deployment config, srcFilesystem vs srcTeamSite

Valentine

I am just curios, what is the difference between these two?

When should I use one or another?

sourceFilesystem
sourceTeamsite

Adam Stoller

Use sourceTeamsite when you want to deploy the differences between two TeamSite areas (usually done with either two editions, or one edition and the staging area). The differences take place completely on the source side, resulting in essentially a filelist, the contents of which can then get pushed to the target machine.

Use sourceFilesystem without a filelist when you either do not have a complete list of all files you want to deploy, or you want to synchronize the target machine from the source machine with a complete diff (that takes place across the network) before deploying the files which are considered changed.

Use sourceFilesystem with a filelist when you have a complete list of all files you want to deploy and you do not wish to perform a cross-network comparison of the data to be deployed.

There are pros/cons to each approacch - the matrix of which is kind of difficult to provide since there are quite a lot of features and functions that interact with one another. For instance, if you are doing filelist deployments - you don't want to use the pending queue feature. If you are using sourceTeamsite deployments, you probably don't want to use pending queue feature either - unless you are using an external process for managing the selection of current and previous areas so that you only use a common base level for previous area until a new base level has been established.

That may not answer all your questions, but hopefully it provides sufficient information to think about and answer some of your questions

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

runtime resources.JPG