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

document root remap

curiousmaverick

Hey,

When we may want to do a document root remap on a branch by branch basis?

Find more posts tagged with

Comments

Adam Stoller

Hey,

When we may want to do a document root remap on a branch by branch basis?

Hey - learn to phrase questions so that they make sense.

curiousmaverick

Hey Ghoti,

Please see TS admin guide 6.7.1, page number 197 under heading Document Roots.

"TeamSite maps the initial Web server directory structure (the document root) of
workareas to the top level of the workarea directory by default. You may, however, want
to move the document root, or group types of files together for improved clarity,
convenience, or efficiency. On a branch-by-branch basis, the TeamSite proxy server
allows you to remap the document root anywhere within the workarea directory. It also
allows you to define mappings directly to subdirectories within workareas."

Adam Stoller

Hey Ghoti,

Please see TS admin guide 6.7.1, page number 197 under heading Document Roots.

"TeamSite maps the initial Web server directory structure (the document root) of
workareas to the top level of the workarea directory by default. You may, however, want
to move the document root, or group types of files together for improved clarity,
convenience, or efficiency. On a branch-by-branch basis, the TeamSite proxy server
allows you to remap the document root anywhere within the workarea directory. It also
allows you to define mappings directly to subdirectories within workareas."

Oh - that's what you were asking about - it was not clear from the initial terse posting. However, since you have all that information such as [indent]"You may [...] want to move the document root, or group types of files together for improved clarity, convenience, or efficiency.[/indent]I'm still not entirely sure what your question is.

Perhaps you're looking for something like this?

Some customers don't like to have "clutter" at the top-level of their workarea - so instead, the workarea contains only things like:

This wouldn't be a big issue if the web server also had the same directory structure - but instead, they often have 'htdocs' map directly to the root of the web server directory structure - so you have to use proxies in TeamSite to make sure that link and image references (and such) can be written the way they need to be for the production server, but mapped correctly to work within TeamSite.Personally, I consider it a mistake to do that kind of mapping unless absolutely necessary. Maintaining a consistency for all the directory structures greatly simplifies many aspects of an implementation - and also tends to make it easier for users of the system too (though not in all cases).

curiousmaverick

Thanks Ghoti. I didn't have a practical example of why the remapping may be needed. Apology for not being clear in my first post.