README.md 1.91 KB
Newer Older
rees_s's avatar
rees_s committed
1 2
# Overview

rees_s's avatar
rees_s committed
3
This is the **wica-links** git repository which provides a system for linking
4 5
from the Wica landing pages on various wica servers to the relevant wica displays
(which are maintained and deployed in separate Git repos).
rees_s's avatar
rees_s committed
6 7 8 9

Since April 2021 this project supports the displays that have been created for
the ILK Upgrade project.

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
# Supported Servers

The following autodeploy servers will be AUTOMATICALLY triggered by publications from this project when the 
project is installed as generally anticipated, ie on a machine running inside the PSI Office Network:

* [GFA Wica External Server](https://wica.psi.ch:8443)
* [GFA Wica Production Server](https://gfa-wica.psi.ch:8443)
* [GFA Wica Development Server](https://gfa-wica-dev.psi.ch:8443)
* [GFA ILK Production Server](https://gfa-ilk-prod.psi.ch:8443)
* [GFA ILK Development Server](https://gfa-ilk-dev.psi.ch:8443)

The following autodeploy servers will can NOT be automatically triggered by this system as they are unreachable
from PSI's office network:

* [PROSCAN ILK Development Server](https://proscan-ilk.psi.ch:8443)
* [HIPA ILK Production Server](https://hipa-ilk.psi.ch:8443)

(To make updates on the above systems it is necessary to make the deployment manually by starting a
browser inside the relevant machine network and navigating to the the autodeploy server's service
configuration page.)

rees_s's avatar
rees_s committed
31 32
# How to deploy

33
Edit the **'dev/index.html'**, **'ext/index.html'**, **'prod/index.html'** and '**ilk/index.html'**
rees_s's avatar
rees_s committed
34 35
files in the src directory as required. When ready for deployment on the
associated servers use the command below:
rees_s's avatar
rees_s committed
36 37 38 39
```
  npm run dist_publish_all
```

rees_s's avatar
rees_s committed
40
This will push these directories to the respective branches on the GitLab
41 42
Server, and send a command to the relevant autodeploy servers to download
and install the required branch to the local filesystems.
rees_s's avatar
rees_s committed
43

rees_s's avatar
rees_s committed
44 45 46
# Project Changes and Tagged Releases

* See the [CHANGELOG.md](CHANGELOG.md) file for further information.