Verified Commit f788bea0 authored by Raphaël Flores's avatar Raphaël Flores
Browse files

Update readme. GNP-5941.

parent 7997cca1
......@@ -102,7 +102,7 @@ Then run `yarn start` to start the app, using the proxy conf to reroute calls to
The application will be available on:
- <http://localhost:4000/rare-dev> for RARe (runs with: `yarn start:rare` or simply `yarn start`)
- <http://localhost:4000/rare-dev> for RARe with basket (runs with: `yarn start:brc4env`)
- <http://localhost:4000/brc4env-dev> for RARe with basket (runs with: `yarn start:brc4env`)
- <http://localhost:4100/wheatis-dev> for WheatIS (runs with: `yarn start:wheatis`)
- <http://localhost:4200/data-discovery-dev> for DataDiscovery (runs with: `yarn start:data-discovery`)
......@@ -242,10 +242,10 @@ Harvesting (i.e. importing JSON documents into Elasticsearch) consists in creati
To create the index and its aliases execute the script below for local dev environment:
```sh
./scripts/index.sh -app rare|wheatis|data-discovery --local
./scripts/index.sh -app rare|brc4env|wheatis|data-discovery --local
```
The -app parameter will trigger a harvest of the resources stored in the Git LFS directories `data/rare`, `data/wheatis` and `data/data-discovery` respectively.
The `-app` parameter will trigger a harvest of the resources stored in the Git LFS subdirectories `data/rare` and `data/data-discovery` filtered or not (`wheatis` and `brc4env` rely on `data-discovery` and `rare` data respectively).
## Indices and aliases
......@@ -287,7 +287,7 @@ In case of testing configuration from the config server, one may use a dedicated
## Building other apps
By default, the built application is RARe (without basket, i.e. without the possibility to add accessions to a basket and create an accession order on the rare-basket application). But this project actually allows building other applications (RARe with basket and WheatIS, for the moment, but more could come).
By default, the built application is RARe (without basket, i.e. without the possibility to add accessions to a basket and create an accession order on the rare-basket application). But this project actually allows building other applications (RARe with basket, WheatIS and DataDiscovery for the moment, but more could come).
To build a different app, specify an `app` property when building. For example, to assemble
the WheatIS app, run the following command
......@@ -316,8 +316,8 @@ You can also run the backend RARe application with basket support using
Adding this property has the following consequences:
- the generated jar file (in `backend/build/libs`) is named `wheatis.jar` (resp. `brc4env.jar` instead of `rare.jar`;
- the Spring active profile in `bootstrap.yml` is `wheatis-app` (resp. `brc4env-app`) instead of `rare-app`;
- the generated jar file (in `backend/build/libs`) is named `wheatis.jar` (resp. `brc4env.jar` instead of `rare.jar`);
- the Spring active profile in `bootstrap.yml` is `wheatis-app` (resp. `brc4env-app`) instead of `rare-app`);
- the frontend application built and embedded inside the jar file is the WheatIS frontend application (resp. the RARe application with basket support) instead of the RARe frontend application, i.e. the frontend command `yarn build:wheatis` (resp. `yarn build:brc4env`) is executed instead of the command `yarn:rare`.
Since the active Spring profile is different, all the properties specific to this profile
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment