Multiple targetFileSystems

Hi Guys,

Is it at all posible in TeamSite to deploy from one branch to multiple branches? That is, if you are hosting a number of sites in TeamSite but want to share a common resource for all the sites and you have set up, each site on a branch. When you publish the resource on a particular branch you want it to also go to the other branches as well when your production web server is hosting a number of web sites on the same machine. Thanks.

Find more posts tagged with

Comments

Adam Stoller

I'm not sure exactly what you're asking here. Can you perhaps try to provide a better "picture" of your scenario (or even draw a real picture with something like Visio - paste it into a word document and then attach the word document?)

How many servers are involved here? one (loop-back)? two-or-more (fan-out)? something else ?

What is the structure of this "common resource" ?
Does it really have to be deployed to multiple branches within TeamSite or can it be referenced from a single common branch instead?
Do you just need to copy submitted files on one branch to multiple branches on the same server? (this could be accomplished via workflow updatetasks or externaltask scripts doing file copies or via OD)

With the details so sparse - any response is going to be shooting in the dark and quite possibly going far astray.

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

Tan Nguyen

Hi Fish,

I'll try to clarify this as best I can, if you are still unable to picture the scenario I'll try to draw up a diagram.

default
|
main
|
www.test1.com
| |
| WORKAREA
|
www.test2.com
|
WORKAREA

In TeamSite we have 2 branches. 1 being for site www.test1.com and the other being www.test2.com.

On our production web server, we are hosting two sites www.test1.com and www.test2.com. (There is only 1 production web server hosting 1 sites)

Normally when we publish content we would publish content from the branch www.test1.com to the site www.test1.com and like wise with the second branch to the second site.

The question is, is it possible to set up TeamSite OpenDeploy to publish a piece of content from the first branch www.test1.com to the 2 sites set up on our prouduction server?

So, only 1 piece of content going to www.test1.com and www.test2.com

Hope that clarifies it abit.

Thanks

Adam Stoller

There is nothing intrinsically stopping you from specifying a source area of site 1 (in TeamSite) and a target area of site 2 (on the web server). This can be done with multiple definitions in a single configuration file that is used for directory comparison deployments or a separate definition (usually, but not absolutely) in a separate configuration file used for filelist deployments.

However, if you truly have common deliverables for multiple sites - it would probably make more sense to have it separated in at least the source side (TeamSite) if not both sides (TeamSite and Web site) to be able to manage it independently of either site in specific (and you might get additional sites later on that can also make use of it). For example, one could have a separate branch for images and deploy it to a separate target location for images and you can set up proxies in both TeamSite and your web server to look for '/images/...' in the common area rather than than a site-specific area.

The difficulty would be trying to deal with a flielist deployment that needs to be divided across multiple target areas -- to do that, you'd still want separate definitions (one for site-specific and one for site-generic) and you'd want to pre-process your filelist to split it up into two file lists and provide the site-specific entries to the site-specific definition and the site-generic entries to the site-generic definition.

OpenDeploy doesn't "know" anything about the source or target area relationships other than what's it told to do when transferring content from one to the other -- if you told it to deploy *everything* from site1 in TeamSite to site2 on your webserver - it will gladly do so - most likely mucking up site2 on your webserver in the process - but would be your fault for telling it to do that as opposed to its fault for following your instructions.

Comprende?

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