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; } } }

using Publish LiveSite Content WF for everything

nipper

OK, since LiveSite gets published to a different folder (served by TomCat) from the other content (served by Apache)I started out with using 2 WFs, one to push the /site folder and one for other assests. Not the best approach

So I want to integrate everything into the PLSC-WF (Publish LiveSite Content Worflow). I am thinking that I change customer-teamsite-resource-config.xml and add 2 more targets (Production and Development content) , filter out the appropriate paths from the deployments and then add 2 more steps in the WF, DeployTestContent and DeployProdContent

I know I could do this easier by just hardcoding a deployment step, but I am trying to do things "right:".

Does this seem reasonable ? Is there a better approach ?

TIA

Andy

Find more posts tagged with

Comments

Faizi

OK, since LiveSite gets published to a different folder (served by TomCat) from the other content (served by Apache)I started out with using 2 WFs, one to push the /site folder and one for other assests. Not the best approach

So I want to integrate everything into the PLSC-WF (Publish LiveSite Content Worflow). I am thinking that I change customer-teamsite-resource-config.xml and add 2 more targets (Production and Development content) , filter out the appropriate paths from the deployments and then add 2 more steps in the WF, DeployTestContent and DeployProdContent

I know I could do this easier by just hardcoding a deployment step, but I am trying to do things "right:".

Does this seem reasonable ? Is there a better approach ?

TIA

Andy

Hi Andy,

OOTB PLSC workflow can use in different requirement. Its need customization as per the requirement. So without making changes in existing one make a copy of it and make change in this.

There is a knowledge base article for Adding multiple target node (deployment area) in Livesite workflow. Its really very good article. And you can successfully implement it.
You can find it in Autonomy Interwoven support site as Knowledge Base Article: 60255.
It is a little bit customization process and need to run build (make_toolkit).

Thanks

nipper

Thanks, I was on the right track, but it is nice to have it documented. My reqs are a little different, but this should be close enough. All I need to do is figure out the best way to filter /sites to TomCat and other to Apache. That should not be too tough.

Andy