Static Export
m |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | OpenCms is capable of exporting [[Resource|Resources]] into the [[Real File System]]. These files can then be served by a normal web server, without involving any more processing on the side of OpenCms. This is mainly used to increase performance and is called ''Static Export''. | + | OpenCms is capable of exporting [[Resource|Resources]] into the [[Real File System]]. That means that opencms creates a frozen snapshot of a website or parts of a website. These files can then be served by a normal web server, without involving any more processing on the side of OpenCms. This is mainly used to increase performance and is called ''Static Export''. |
| − | OpenCms is not only able to export static files like images from its [[Virtual File System]] - it can also export a complete page, after it has been processed by a [[JSP Template]]. Of course this makes only sense for resources, that do not have to change with each request. Because of this, Static Export can be switched on or off for | + | OpenCms is not only able to export static files like images from its [[Virtual File System]] - it can also export a complete page, after it has been processed by a [[JSP Template]]. Of course this makes only sense for resources, that do not have to change with each request. Because of this, Static Export can be switched on or off for complete folders or individual files by using the ''export'' property. |
| + | |||
| + | Opencms can handle websites where only some pages are exported and some pages are always created dynamically. In such a case, OpenCms will automatically rewrite any links so that references to exportable files will point to their export location but that all other links will still point to the CMS where they are generated dyanamically. | ||
See also: [[Static Export After Publish]], [[Static Export On Demand]] and [[Static Export configuration]]. | See also: [[Static Export After Publish]], [[Static Export On Demand]] and [[Static Export configuration]]. | ||
Latest revision as of 10:22, 21 January 2007
OpenCms is capable of exporting Resources into the Real File System. That means that opencms creates a frozen snapshot of a website or parts of a website. These files can then be served by a normal web server, without involving any more processing on the side of OpenCms. This is mainly used to increase performance and is called Static Export.
OpenCms is not only able to export static files like images from its Virtual File System - it can also export a complete page, after it has been processed by a JSP Template. Of course this makes only sense for resources, that do not have to change with each request. Because of this, Static Export can be switched on or off for complete folders or individual files by using the export property.
Opencms can handle websites where only some pages are exported and some pages are always created dynamically. In such a case, OpenCms will automatically rewrite any links so that references to exportable files will point to their export location but that all other links will still point to the CMS where they are generated dyanamically.
See also: Static Export After Publish, Static Export On Demand and Static Export configuration.
