Make environment configurable outside of provided jars

[txtran]

Jetty version
12.1.7

Jetty Environment
static

Enhancement Description

Hi,
As shown in the examples seen here https://jetty.org/docs/jetty/12.1/programming-guide/server/deploy.html, there is not an easy way to configure a specific environment's context for something like the static deployer. I understand that we have the option to override the StaticAppContext and provide our own setting such as the "dirAllowed" property for the entire server (and not just a specific application via the "app.properties" file). However, that would require us to create our own jar and add it to the classpath.
I wonder if it is possible to provide a more flexible option create the environment dynamically using our own custom StaticAppContext without having to deal with ClassLoader and what not? Thanks.

[joakime]

I don't follow what you are asking specifically for?

We have several deployers already ...

Deployer Module	Environment	Role
static-deploy	static	Will deploy static content only, using StaticAppContext.
core-deploy	core	Which uses the CoreAppContext and has a structure (like a war file) for custom classes, custom XML, custom libraries, static directory, etc.
ee8-deploy	ee8	For Jakarta EE8 WebApps (WAR files, exploded war directories, etc)
ee9-deploy	ee9	For Jakarta EE9 WebApps (WAR files, exploded war directories, etc)
ee10-deploy	ee10	For Jakarta EE10 WebApps (WAR files, exploded war directories, etc)
ee11-deploy	ee11	For Jakarta EE11 WebApps (WAR files, exploded war directories, etc)

Keep in mind that each deployment exists on it's own context-path and is subject to the context matching rules of the ContextHandlerCollection (if the incoming request matches the context, and virtual-hosts, then send request to that context, the request MUST be handled by that ContextHandler implementation)

You cannot have two ContextHandler implementations (eg: CoreAppContext, StaticAppContext, WebAppContext, etc) on the same context-path matching rules. In other words, if you try to deploy webapps/ee8-myapp on context-path of /app and webapps/ee8-admin on context-path of /app with the same virtual-host declaration (or no virtual-host declaration), that would be a bad configuration and the ContextHandlerCollection cannot process a single request for both deployed context's.

[txtran]

I'm asking for a way to not having to create a properties file (https://jetty.org/docs/jetty/12.1/operations-guide/deploy/index.html#web-application-format-static) to disable dir listing for every static app that I deployed to the same context (e.g. "/"). I guess this is doable only with static app because I don't need to separate each static app into its own context. In this case, the "folder" itself serves as a distinct path for the app already and all of them behave the exact same way (which basically just renders the static content). To be very specific, I'm asking for a way to provide a custom version of this:
https://github.com/jetty/jetty.project/blob/jetty-12.1.x/jetty-core/jetty-staticapp/src/main/java/org/eclipse/jetty/staticapp/StaticAppContext.java
without having to create a new jar and add it to the classpath.
You are probably wondering what's the need for me to do something like this. In my case, I'm trying to deploy various HTML contents generated from Mkdocs and make them accessible via a web browser. The HTML contents can come from different sources and can be deployed dynamically independent of each other (under the same "webapps" folder).