Skip to content

Commit 652390e

Browse files
authored
Update README.md
1 parent 236bb01 commit 652390e

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -107,20 +107,21 @@ gradlew integrationTest
107107
- The [Publish docker image](https://github.com/JeffersonLab/container-workflows/blob/main/.github/workflows/docker-publish.yaml) GitHub Action to create a new demo Docker image.
108108

109109
## Deploy
110-
At JLab this app is found at [epicsweb.jlab.org/epics2web](https://epicsweb.jlab.org/epics2web/) and internally at [epicswebtest.acc.jlab.org/epics2web](https://epicsweb.jlab.org/epics2web). However, those servers are proxies for tomcat1.acc.jlab.org and tomcattest1.acc.jlab.org respectively. Use wget or the like to grab the release war file. Don't download directly into webapps dir as file scanner may attempt to deploy before fully downloaded. Be careful of previous war file as by default wget won't overrwite. The war file should be attached to each release, so right click it and copy location (or just update version in path provided in the example below).
110+
At JLab this app is found at [epicsweb.jlab.org/epics2web](https://epicsweb.jlab.org/epics2web/), plus other fiefdom specific subpaths, and internally at [epicswebtest9.acc.jlab.org/epics2web](https://epicswebtest9.acc.jlab.org/epics2web/). However, the epicsweb server is a proxy for `epicswebops9.acc.jlab.org`, `epicswebops99.acc.jlab.org`, `epicswebchl9.acc.jlab.org`, `epicsweblerf9.acc.jlab.org`, `epicswebsrf9.acc.jlab.org` and `epicswebuitf9.acc.jlab.org`. Additionally, the context root for each is adjusted with a prefix such that all servers can be reached from a single namespace. The context root prefixes are `/`, `/ops2`, `/chl`, `/fel`, `/srf`, and `/itf` respectively. Tomcat interprets context roots from _war_ file name unless overridden elsewhere. Therefore each _war_ must be prefixed with `<prefix>#`. Use wget or the like to grab the release war file. Don't download directly into webapps dir as file scanner may attempt to deploy before fully downloaded. Be careful of previous war file as by default wget won't overrwite. The war file should be attached to each release, so right click it and copy location (or just update version in path provided in the example below).
111111

112112
A script is provided to automate the deployment. As root run:
113113
```
114114
cd /root/setup
115115
./deploy.sh epics2web {version}
116116
```
117117

118-
Or manually execute:
118+
Or manually execute (CHL fiefdom shown):
119119
```
120120
cd /tmp
121121
rm epics2web.war
122122
wget https://github.com/JeffersonLab/wmenu/releases/download/v1.2.3/epics2web.war
123-
mv epics2web.war /opt/tomcat/current/webapps
123+
mv epics2web.war chl#epics2web.war
124+
mv  chl#epics2web.war /opt/tomcat/current/webapps
124125
```
125126

126127
## See Also

0 commit comments

Comments
 (0)