LSCS Deployment filtering

nipper

OK, trying to deploy /sites, /iw, /templatedata, etc to Tomcat and then /assets, /html (legacy stuff) etc to Apache. Running on 7.3.1 Linux with TS/SP/LSDS/LSCS.

So I added to the production bean:
[php]











-^(//[^/]+)?/iwadmin/main/.*

^(//[^/]+)?/.*?/main/project/WORKAREA/Shared/sites/.*
^(//[^/]+)?/.*?/main/project/WORKAREA/Shared/iwov-resources/.*
^(//[^/]+)?/.*?/main/project/WORKAREA/Shared/iw-resrouces/.*
^(//[^/]+)?/.*?/main/project/WORKAREA/Shared/templatedata/.*
^(//[^/]+)?/.*?/main/project/WORKAREA/Shared/iw/.*
















-^(//[^/]+)?/iwadmin/main/.*
(//[^/]+)?/.*?/main/project/WORKAREA/Shared/assets/.*
(//[^/]+)?/.*?/main/project/WORKAREA/Shared/html/.*








[/php]

But the deployments are not working (often at all). If I send a .page (from /sites) no deployment happens.

From the limited documentation, it really does not list any restrictions. Anyone use this before ? Any unknown issues ?

Rick Poulin

This config doesn't work the way most of us would expect. The intention behind the multiple target nodes is to deploy different LiveSite sites to different targets. There's a "target node" field in your default.site that can only take a single value (I checked; you can't comma-delimit multiple targets). As such, your site can only ever deploy to LiveSiteRuntime OR WebServerRuntime, but not both. Branches will deploy assets outside of /sites to the target nodes of all sites in the branch, meaning that a "silly" way to make this work is to create a dummy site and point it at WebServerRuntime. Thus, your pages for your real site will go only to LiveSiteRuntime, and your static assets will go to both targets.

The only supported + reasonably simple way I know of accomplishing what you're looking for is to change the OD configs as appropriate, i.e. with two <source> structures that look at the same generated filelist but apply different filters to different targets.

That or option 2, which I generally prefer, is to not change the deployments at all and instead configure Apache with virtual directories that go read from the LSDS webapp root for known static root folders, and to keep proxying everything else through LSDS.