Document-directory
From Resin 3.0
(renamed tag to directive) |
|||
| Line 5: | Line 5: | ||
== <[[web-app]]> == | == <[[web-app]]> == | ||
| − | For webapps defined in the [[resin.conf]], we recommend setting an explicit <document-directory>. The | + | For webapps defined in the [[resin.conf]], we recommend setting an explicit <document-directory>. The directive will document your configuration when you need to update it. |
By default, though, the <[[web-app]]> will append the webapp's <code>id</code> to the <document-directory> of the webapp's <[[host]]>. As mentioned above, we do not recommend this configuration because it makes configuration files harder to read. | By default, though, the <[[web-app]]> will append the webapp's <code>id</code> to the <document-directory> of the webapp's <[[host]]>. As mentioned above, we do not recommend this configuration because it makes configuration files harder to read. | ||
Latest revision as of 20:21, 21 February 2006
The <document-directory> is used to specify the location of documents for a <web-app>. For web-apps, <document-directory> is the equivalent of a <root-directory> for a <host>
<web-app>
For webapps defined in the resin.conf, we recommend setting an explicit <document-directory>. The directive will document your configuration when you need to update it.
By default, though, the <web-app> will append the webapp's id to the <document-directory> of the webapp's <host>. As mentioned above, we do not recommend this configuration because it makes configuration files harder to read.
<host>
In general, we do not recommend setting the <document-directory> for the <host>. Set the <root-directory> instead and set the <document-directory> explicitly for each <web-app>
