You are here: Administrators Reference > Site Administration > Static Content Generation > Static Site Architecture > Static Site Main Concepts > Static Site Directory Structures

 

Static Site Directory Structures

When the Static Content Generation module on the dynamic server generates static pages, it duplicates directory structures and filenames when creating files in the dynamic directory tree. For each CommonSpot-generated page on the dynamic server, the Static Content Generation module creates either a redirect file (for dynamic pages) or an HTML version of the page (for static pages).  The page-generation timestamps should be the same. The file sizes will obviously differ.

Note that when configuring the Static Content Generation module, CommonSpot prompts for the full path of the directory for generating static content. In the static HTTP server, this directory is typically configured as the root directory for the site.

Also note that CommonSpot supports path names to a shared file system. Except through replication, CommonSpot does not currently provide any means - outside of a shared file system - to transport static files to an HTTP server.

This means that if you want to serve the static content generated on authoring server A on two HTTP servers B and C, you have the following options:

By default, dynamic pages are represented on the static server by files containing JavaScript code to redirect requests to the dynamic server. You can customize this representation by updating redirect-custom.cfm in the site’s root directory on the Authoring server. The file {commonspot-root}/static/redirect-custom.cfm is a sample redirect module containing all of the attributes and available parameters required to override the default redirect mechanism.

 

Related Links


You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).


For technical support:

http://www.paperthin.com/support/