414635 Modular start.d and jetty.base property

Added more info in README.TXT files
This commit is contained in:
Greg Wilkins 2013-08-19 13:22:02 +10:00
parent 84df81c288
commit bead95314a
3 changed files with 40 additions and 1 deletions

View File

@ -0,0 +1,26 @@
This start.d directory contains modular ini files that are appended to the effective command line
used to start jetty by the command:
java -jar start.jar
The modules are executed in alphabetic order and the 'NNN-' prefixes are a convention to make that ordering
explicit regardless of module name.
All modules ending with '.ini' will be executed and it is a convention that disabled modules are renamed to
end with '.ini.disabled'. The start.jar mechanism can be used to enable/disable modules with commands like:
java -jar start.jar --enable=ssl --enable=spdy
Note that the numeric prefix can be skipped in such commands.
The ini modules have a simple dependency mechanism so a module can declare if it depends on or conflicts with
other modules. For example the spdy module includes the entries:
EXCLUDE=https
DEPEND=npn,ssl
This says that spdy cannot be used with the https module (both use the same port and spdy provides https) and
that the npn and ssl modules must also be enabled.

View File

@ -3,5 +3,10 @@ This directory is scanned by the demo WebAppDeployer provider
created in the etc/jetty-demo.xml file and enabled by the
start.d/900-demo.ini file.
For normal deployment, use the webapps directory.
To disable the demo, either remove the start.d/900-demo.ini or issue the following command:
java -jar start.jar --disable=demo
For normal webapp deployment, use the webapps directory.

View File

@ -23,3 +23,11 @@ only the XML is deployed (which may use the war in its configuration).
This directory is scanned for additions, removals and updates
for hot deployment.
To configure the deployment mechanism, edit the files:
start.d/500-deploy.ini
etc/jetty-deploy.ini
To disable the auto deploy mechanism use the command:
java -jar start.jar --disable=deploy