Hi,
I'm organising the Design folder with subfolders where each Organisation entity (think lots of them) will have their own. I then link the respective subfolder to their branch of the asset tree so they can easily manage their branch without needing to see the whole tree.
Is there any reason why I need to apply more than one generic URL to the design folder?
Every site would have their design in:
cms.mycompany.com/_designs/ou/oentity/…
and their domain will usually be:
www.oentity.mycompany.com/
I know the issue popped up in a few threads but I can't remember why people were really keen to have design with the right domain name?
Experiences and advices welcome.
Cheers, Wombat
Edited: spelling… 
Your designs will get the right domain name anyway (by virtue of being linked under the asset map in another location).
I just like it for cleanliness, really. There's no technical reason for it, though.
Nope, I don't link them under the site, but at the same level therefore the design doesn't have another url.
Entity (Folder)
|_Entity Designs (Folder - Linked)
|_Entity Site (Site asset)[quote]I just like it for cleanliness, really. There's no technical reason for it, though.[/quote]
There is a technical reason against it though, as it takes a while to cascade a new URL each time you add a new entity.
If you use the special static files url in your system, most of the files get served off a single generic url anyway, so I can't forsee any issues that should stop you structuring it this way.
[quote]If you use the special static files url in your system, most of the files get served off a single generic url anyway, so I can’t forsee any issues that should stop you structuring it this way.
[right][post=“9136”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks.
As for static files, we’re doing it at the Apache level and point to a single vhost.
Just as a curiosity though, where can I read about the Static URL configuration that appeared in 3.8?
Here is some info from the 3.80RC1 changelog:
Static Site URL
A new system configuration option has been added to MySource Matrix that allows you to define a static URL for the system. The static URL can be used to allow alternate web servers to serve static content located in the data/public directory of MySource Matrix.
The static URL is primarily used for file assets when they go live with public read access. Instead of setting the __data URL for a file MySource Matrix will use the static URL, allowing an alternate web server to serve the files and take some strain off the main Apache web server.
This is a system-wide setting (as there is only one data/public location) and the static URL needs to point to the data/public location. You still need to configure the __data alias in Apache so that the Java applet and any JavaScript code can access that location as well.