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

Custom livesite deploy mechanism

RonaldV

I have been trying to understand what the ootb livesite publish workflow does. But this seems to be very complex.

Would it be possible to write a custom workflow/script that deploys the livesite content to the correct locations? Maybe using the ootb deploy-configs?

Does anybody know what is going on behind the screens of the ootb workflow?

F.i., what is (technically) happening in:
- workflow.task.HeadlessDeploymentTask?
- workflow.task.DependencyTask?
- workflow.task.DeploymentTask?
- workflow.task.SetMetaTagsTask?
- workflow.task.TaxonomyTransformationTask?
- workflow.task.ValidationTask?

Find more posts tagged with

Comments

vpatel

Which version of TS are you working on? Also, are you using LSDS only or LSCS as well?

RonaldV

Yes sorry: Ts72 incl. LSDS & LSCS

vpatel

Yes sorry: Ts72 incl. LSDS & LSCS

So if you are on 7.x+, you could just create a custom deployment that will do following:

1. Deploy ALL of your files to target location(s) -- i.e. static assets (images, flash, js, css, etc.) to some web server and SP/dynamic assets (.page, sitemap, taxonomy, DCR XMLs, etc.) to the LSDS server.

2. Create your cache.**** filelist (which contains a file list of area-relative paths to ALL .page files only) and deploy it to LSDS-home/runtime/web/sites

3. Deploy ALL (or files that you wish to use for Targeting / Personalization) to LSCS using the LSCS startDeployment.bat. If you are a Java-Pro then look inside of that bat file and you can call that Java class directly from your external task if you'd like.

With 7.2 -- with LSCS -- you NO longer need the taxanomies, metadata, etc. deployments going into the DB. You just need to deploy all of this to LSCS -- no DD no nothing... Engr'ing has left some of these DB Deployments in place for backwards compatibility. Eventually they will be taken out.

HTH!

RonaldV

Thank you. That is a VERY helpful reply. I'll investigate and might get back to you. ;-)

RonaldV

Brilliant!

What you wrote answers my questions. As an extra one could use StartDeploy.trigger() to start the lscs deploy from within java, as explained in Chp 5 of LiveSite Content Services Technical Reference Guide V7.1.

@Iwov: would you care to document this properly?