Regex in iw.cfg for docroot

Husna

Hi All,

I had all the images to be browsed in a template present in a particular folder initially so I configured the docroot in iw.cfg to that particular folder.
Now the images have also been placed in another folder and the images to be browsed in the templates can be present in any of these 2 folders.
I need to configure my docroot as a regex.
Can someone please help me out as to how can we configure a regex docroot in iw.cfg

Existing docroot configures as:
_docroot=/assets/SiteAssets

New docroot to be configured as:
_docroot=/assets/SiteAssets or _docroot=/assets/Merchandising

Thanks in advance.

Adam Stoller

Hi All, I had all the images to be browsed in a template present in a particular folder initially so I configured the docroot in iw.cfg to that particular folder. Now the images have also been placed in another folder and the images to be browsed in the templates can be present in any of these 2 folders. I need to configure my docroot as a regex. Can someone please help me out as to how can we configure a regex docroot in iw.cfg Existing docroot configures as: _docroot=/assets/SiteAssets New docroot to be configured as: _docroot=/assets/SiteAssets or _docroot=/assets/Merchandising Thanks in advance.

Docroot, to the best of my knowledge, does not support regex's - it is intended to do a simple path mapping for documents, and not specifically for images).

If this change is for different branches, you can configure tsettings for each specific branch in iw.cfg - however I don't think that's what you want either.

If the images get deployed into both SiteAssets and Merchandising directories on the web server - the URI for those images should include that leading directory - and you could just use /assets as the mapping point.

If the images from both directories get deployed into the same directory (e.g.: /images) on the web server - that is (IMO) a bad design - the TS directory structure should map 1:1 with the web server directory structure.

There are many other possibilities here, both in terms of design and issue resolution - but without knowing your TS and web server directory structures and where/when you're having an issue (and other assorted pieces of information) - it's kind of difficult to pinpoint a true resolution for you.