-
Notifications
You must be signed in to change notification settings - Fork 0
/
workflow.conf.template
34 lines (27 loc) · 1.78 KB
/
workflow.conf.template
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
## WORKFLOW ##
# TODO FIXME: any opinion which of these we should use?
redirect 301 ${WORKFLOW_PATH} ${WORKFLOW_PATH}/
# RewriteRule ^/${WORKFLOW_PATH}$ /${WORKFLOW_PATH}/ [R,L]
# websocket via HTTP (alternative might be mod_proxy_wstunnel, but I'm unsure)
ProxyPass ${WORKFLOW_PATH}/omnifaces.push/ http://${WORKFLOW_CONTAINER}:${WORKFLOW_HTTP_PORT}${WORKFLOW_PATH}/omnifaces.push/ retry=0 timeout=600 upgrade=websocket
#ProxyPassReverse ${WORKFLOW_PATH}/omnifaces.push/ ws://${WORKFLOW_CONTAINER}:${WORKFLOW_HTTP_PORT}${WORKFLOW_PATH}/omnifaces.push/
# TODO add a variable in Dockerfile to switch the protocol being used on the backend
# proxy to via AJP
ProxyPassMatch ^${WORKFLOW_PATH}/(.*)$ ajp://${WORKFLOW_CONTAINER}:${WORKFLOW_AJP_PORT}${WORKFLOW_PATH}/$1 retry=0 timeout=600
<LocationMatch ^${WORKFLOW_PATH}/(.*)$>
ProxyPassReverse ajp://${WORKFLOW_CONTAINER}:${WORKFLOW_AJP_PORT}${WORKFLOW_PATH}/$1
Require all granted
</LocationMatch>
# proxy to via HTTP
#ProxyPass ${WORKFLOW_PATH}/ http://${WORKFLOW_CONTAINER}:${WORKFLOW_HTTP_PORT}${WORKFLOW_PATH}/ retry=0 timeout=600
#ProxyPassReverse ${WORKFLOW_PATH}/ http://${WORKFLOW_CONTAINER}:${WORKFLOW_HTTP_PORT}${WORKFLOW_PATH}/
# TODO sanity check me: this would redirect / to workflow, right?
# commented out, because we need to decide where to send people, see above
#RewriteRule ^/$ /${WORKFLOW_PATH}/ [R,L]
## ITM ##
# TODO: commented out for a reason? do we never need this?
#ProxyPass /${ITM_PATH}/ ajp://${ITM_CONTAINER}:${ITM_AJP_PORT}/${ITM_PATH}/ retry=0
#ProxyPassReverse /${ITM_PATH}/ ajp://${ITM_CONTAINER}:${ITM_AJP_PORT}/${ITM_PATH}/
#
#RewriteRule ^/${ITM_PATH}$ /${ITM_PATH}/ [R,L]
#RewriteRule ^/$ /${ITM_PATH}/ [R,L]