Closed jesse-gallagher closed 3 years ago
Turns out I actually did this a while ago. However, it's done by tying OpenLibertyRuntime to Domino-specific knowledge, which it otherwise doesn't need. This would be better done via a command or extension in .adminnsf
.
The reverse-proxy extension in
.adminnsf
contains code that reads the HTTP settings for the current Domino server, and this code could be reused to eliminate the need to manually setDomino_HTTP
for the user registry. This could be written into server.env dynamically during deployment.