Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
.Page deployment with DCR DATUM type
HarryPaul
Hi,
I have following query with respect to end user production environment.
1. I have a page which consists of DCR DATUM types. Now when i deploy my.page my understanding is that i need to deploy the referenced DCR as well.
Or is there any other better way by which DCR data can be used in the Production environment.
2. In continuation to above i have following directory structure in my TeamSite
XYZ
|--Country1 Branch
-----WORKAREA
-------WKName
----------Images
----------Javascript
----------Sites
------------Country1Site
|--Country2 Branch
-----WORKAREA
-------WKName
----------Images
----------Javascript
----------Sites
------------Country2Site
Now i want my end user production environment structure to be like
|--web
------country1
--------Images
--------Javascript
--------templatedata
------country2
--------Images
--------Javascript
--------templatedata
------Sites
--------Country1Site
--------Country2Site
How my .pages in Country1Site can access images/javascript/templatedata in country1 folder. Or should I move all my assets in site folder? Which i think is not possible as the site folders can only have .pages.
I hope i have made myself clear and not confused enuf. Please help me with this.
Thanks
Harpreet
Find more posts tagged with
Comments
kmu
Still interested in some input on your questions?
The DCR must of course be deployed - in the runtime the xml files are being picked up again. That's what you wanted in the first place, isn't it? Thus you can change it in one place and reference it several times throughout the website.
Regarding your end user production environment structure - depending on the webserver you are using you can remap folders more or less easily to reflect any directory structure. It is good practice to route the LiveSite runtime through lets say an Apache using its proxy and rewrite modules to tweak the directories, query strings etc. a bit. The same can be done (though more painful) using IIS.