Add gdcc/nginx:unstable image and dev_nginx container for IntelliJ Payara plugin workaround #10088
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Adds a nginx container to the docker setup. This could be used for various proxying stuff, but it is primarily added to work around a problem with the IntelliJ Payara plugin. It doesn't allow remote redeployment in case the Payara admin is served via HTTPS using a self-signed certificate, which is the case of the default dataverse container installation.
For more context see this discussion: https://dataverse.zulipchat.com/#narrow/stream/375812-containers/topic/faster.20redeploy
This nginx configuration provides an HTTP endpoint at port 4849, and proxies requests to the Payara admin console's HTTPS 4848 endpoint.
Special notes for your reviewer:
You need IntelliJ IDEA Ultimate Edition to have remote deployment available in the Payara plugin.
Suggestions on how to test this:
Build and start the Dataverse containers:
Applications
.Run > Debugging actions > Update '...' application (cmd+f10) > Redeploy