You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2023. It is now read-only.
I want to run the docker images on a machine that already is hosting web services. My idea would be to use apache proxy to forward from a subdomain to the non-standard http port of the docker. However, I found that the job.notifyURL seems to be set to https://localhost/.... Besides allowing specifying non-standard ports, it might be better to generalize this to also allow different hosts.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I want to run the docker images on a machine that already is hosting web services. My idea would be to use apache proxy to forward from a subdomain to the non-standard http port of the docker. However, I found that the
job.notifyURL
seems to be set tohttps://localhost/...
. Besides allowing specifying non-standard ports, it might be better to generalize this to also allow different hosts.The text was updated successfully, but these errors were encountered: