nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multi Site Deployment in single RunTime

sumitk

Hi,

I am relatively new to LiveSite and LiveSite RunTime environment. I have a requirement to deploy microsites onto a single LiveSite Runtime (one target server). My question is, is it feasible and if yes, where should I deploy all microsites under RunTime so that sites can be accessed?

I have gone through the LiveSite Documentation wherein I got the information of deployment on multi environments. But I am not getting any info related to single RunTime Environment.

Appreciate any pointers in this direction. Thanks in advance.

PS: Each microsite is on a seperate branch.

Env Details:

TeamSite : 7.1 Windows

LiveSite : 7.1

OpenDeploy :7.1

Find more posts tagged with

Comments

vpatel

All sites being deployed to a single runtime is the default OOTB behavior -- if you are using the OOTB PLC Workflow. What is the reason for having separate branches for different microsites? You may run into "asset collision" with that approach.

tanguyr

Hi Sumtik,

Yes, this should work out of the box without any problems. On the runtime, sites are deployed under $[ls-home]/runtime/web/sites, one per folder - so $[ls-home]/runtime/web/sites/myfirstsite, $[ls-home]/runtime/web/sites/anothersite, etc etc

You write that "PS: Each microsite is on a seperate branch." - be careful! Each site will be stored in its own branch, but they will all be deployed to the same basic location on the runtime. What this means:

In teamsite
branch1/WORKAREA/[waname]/sites/myfirstsite
branch2/WORKAREA/[waname]/sites/anothersite

On LSRT:
$[ls-home]/runtime/web/sites/myfirstsite
$[ls-home]/runtime/web/sites/anothersite

Now, let's say you wind up with a folder named "anothersite" in the sites folder of branch1 (could easily happen if somebody did a "copy to" operation in contentcenter). User then deletes this folder in branch1 **AND SUBMITS THE DELETE VIA WORKFLOW** - workflow will happily delete all of "anothersite" on the runtime! This isn't a weakness in the tool, it's just user error, but it did happen to us once and it wasn't fun.

Regs,
/t

PS: note that we are running on an older version (1 version ago) of TeamSite/LiveSite than you are, so i'm not sure how applicable this is to you

sumitk

Thanks for the response. I am not using the OOTB Publish Workflow. I am trying to build up a POC in which I am creating my own WF to deploy sites. And as far as the assets are concerned, do not worry about it. I am gonna take care of it.

On LSRT:
$[ls-home]/runtime/web/sites/myfirstsite
$[ls-home]/runtime/web/sites/anothersite

As per your quote, I did the deployment under sites folder but my second site is not getting recognized.

I am getting the error

ERROR [EmbeddedDataMapping] Site directory collision [color=blue]myfirstsite with site anothersite, Site anothersite will not be

loaded[/color]

What could be wrong here?

Thanks,

Sumit

Rick Poulin

The Site Directory property is set in the default.site file. Seems you've picked the same value for both, which is one of those things that the UI will let you do when using different branches. Make sure to set one to /myfirstsite and the other to /myothersite.

sumitk

The Site Directory property is set in the default.site file. Seems you've picked the same value for both, which is one of those things that the UI will let you do when using different branches. Make sure to set one to /myfirstsite and the other to /myothersite.

Yes, that was the mistake I was doing. Finally, I figured it out where I was going wrong.

Thanks for your assistance.

Cheers,

Sumit