Summary: | Need a conventions document | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Rodent of Unusual Size <coar> |
Component: | Documentation | Assignee: | HTTP Server Documentation List <docs> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.5-HEAD | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Rodent of Unusual Size
2015-04-15 20:38:23 UTC
Oh, and come up with (and use) some consistent argument-type keywords, like * FILE-PATH (and describe in the user conventions that these are ServerRoot- relative if not absolute) * KEYWORD (like "temp", "permanent", "ExecCGI", ...) * REGEX or PATTERN * GLOB (do we have anything that does this?) * EXPRESSION * IDENTIFIER (like the name given to a rewrite map specification) * URL (local or full) There should be a way of indicating that an argument can interpolate variables or regex group values, such as the first argument to RewriteCond or the second argument to RewriteRule (or any of the *Match directives). Noodling in the bug report.. This should go in the https://httpd.apache.org/docs-project/ site, which is mostly still accurate, but is somewhat light on detail, and doesn't make it exactly easy to get started. A style/convention guide would indeed be a very good start to that. |