[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jetty-dev] trying to get jetty properties honored in private SSL module
- From: Brian Reichert <reichert@xxxxxxxxxxx>
- Date: Tue, 10 Oct 2017 14:52:40 -0400
- Delivered-to: email@example.com
- User-agent: Mutt/1.5.9i
On Tue, Oct 10, 2017 at 11:15:31AM +1100, Greg Wilkins wrote:
> note that there is also an [ini] section within modules, that can be used
> to set properties whenever the module is activated, as apposed to the
> [ini-template] section, which as Chris says is only a template for
> generating an ini file.
Gee, well, that nails it. Putting my settings in the [ini] section
does seem to do what I want.
I failed to notice the distinction, and assumed the pre-populated
[ini-template] was the what I was supposed to use. :/
> Typically [ini] sections are discouraged as they can be hard to modify, but
> they are appropriate in some circumstances. Often they are used with the
> ?= syntax, so the property is set only if it has not already been set on
> the command line or in an ini file.
That's a neat hack I was unaware of...
> An example is from the new conscrypt module that sets the version and
> provider with:
> > conscrypt.version?=1.0.0.RC10
> > jetty.sslContext.provider?=Conscrypt
Brian Reichert <reichert@xxxxxxxxxxx>
BSD admin/developer at large