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
If Pathway Commons data and files have been updated since this app's last built and run,
48
+
or you simply want to connect to a different PC2 instance (and set PC_URL environment variable),
49
+
then the file `src/server/graph-generation/generic-physical-entities/generic-physical-entity-map.json`
50
+
needs to be updated. Also, purge the RethinkDb db tables or simply switch the database.
51
+
52
+
The following script downloads and processes physical_entities.json.gz file from Pathway Commons:
53
+
```sh
54
+
cd src/scripts/generic-entity-mapping/
55
+
PC_VERSION=v10 sh update.sh
56
+
```
57
+
(PC_VERSION should be set to the name of a sub-directory in `www.pathwaycommons.org/archives/PC2/`)
44
58
45
59
## Run targets
46
60
@@ -86,15 +100,15 @@ Notes:
86
100
87
101
### Run image hosted on Docker Hub using Docker Compose
88
102
89
-
Pathway Commons maintains a [Docker Hub](https://hub.docker.com/) image for [app-ui](https://hub.docker.com/r/pathwaycommons/app-ui/) that is automatically built each time a commit is pushed to GitHub.
103
+
Pathway Commons maintains a [Docker Hub](https://hub.docker.com/) image for [app-ui](https://hub.docker.com/r/pathwaycommons/app-ui/) that is automatically built each time a commit is pushed to GitHub.
90
104
91
105
To run the GitHub development branch:
92
106
93
107
```sh
94
108
docker-compose --file docker-compose.yml up --detach
95
109
```
96
110
97
-
Access the app instance at port `9090`.The default configuration declared in `docker-compose.yml` also runs a [rethinkdb](https://hub.docker.com/_/rethinkdb/) image; access the UI at port `8020`.
111
+
Access the app instance at port `9090`.The default configuration declared in `docker-compose.yml` also runs a [rethinkdb](https://hub.docker.com/_/rethinkdb/) image; access the UI at port `8020`.
98
112
99
113
Notes:
100
114
- References:
@@ -145,7 +159,7 @@ Students who work on the repo should follow these instructions for each feature
145
159
1. Using the console: `git checkout name-of-feature`, `git merge development`
146
160
1. Using GitUp:
147
161
1. Make sure your `HEAD` is the newest commit of your feature branch: Right-click the latest commit on `name-of-feature` branch and select `Checkout "name-of-feature" Branch`
148
-
1. Right-click the latest commit of the `development` branch and select `Merge into Current Branch`
162
+
1. Right-click the latest commit of the `development` branch and select `Merge into Current Branch`
149
163
1. Push your commits to GitHub:
150
164
1. Note: You can push as often as you'd like so that your code is backed up on GitHub. You *must* push everything before you make a pull request.
151
165
1. Using the console: `git push`
@@ -166,3 +180,4 @@ Students who work on the repo should follow these instructions for each feature
166
180
1. For a breaking API change, run `npm version major.`
167
181
1. For a specific version number (e.g. 1.2.3), run `npm version 1.2.3`.
0 commit comments