This section outlines the content folder that Phoenix uses in conjunction with the database to store dynamic content and user submitted files.
This topic contains the following sections.
/content
When we refer to the content folder, we generally mean the folder that Phoenix is using to store user uploaded files and other dynamic content that is stored outside of the database. The physical location of the content folder can be changed, but the heirarchy of sub-folders is maintained by Phoenix.
The location of the the content folder is defined in IIS by creating a virtual folder called content that points to a folder on your server. At run-time, Phoenix maps the virtual folder ~/content to obtain the physical location of the content files on your machine.
/content/logs
This folder contains the active log file as well as all log files that have been archived. New messages are appended to phoenixlog.xml until the archive condition as set by LogArchiveMethod in appSettings.config is met. The current log file is renamed by adding the current time to the filename, and a new log file is created. Once a log file has been archived, it is no longer used by the system and can be deleted by the system administrator directly, or from within Phoenix using the System Error Log page.
See also the Xml structure of Phoenixlog.xml.
 Caution: |
|---|
|
Please ensure that ASP.NET has write access to this folder. |
 Tip: |
|---|
|
Messages are written to the log file using the methods of the PhoenixLog class. |
/content/services
Contains...
/content/temp
The temp folder is used to store temporary files generated by the system, as well as files that have been uploaded by users but not yet committed to a workspace. Old files are removed by an external process (see PhoenixFileService) that periodically traverses this folder and permanently deletes all files older than a predefined time interval.
/content/styles
This folder contains cascading style sheets (.css) and related image files.
/content/thumbnails
This folder contains thumbnails of all images, layers and maps that have been created in the system.
/content/users
Contains...
/content/workspaces
The workspaces folder is comprised of subfolders; each one represents a single workspace and its assets. The name of each workspace folder directly corresponds to the ID of the workspace.
