@@ -6,7 +6,8 @@ inspect the corresponding results.
6
6
Table of contents:
7
7
8
8
* [ Preface] ( #preface )
9
- * [ Getting Started] ( #getting-started )
9
+ * [ Getting started] ( #getting-started )
10
+ * [ The supporting resources] ( #the-supporting-resources )
10
11
* [ Static, production build] ( #static-production-build )
11
12
* [ Logging in] ( #logging-in )
12
13
* [ Configuration file] ( #configuration-file )
@@ -27,9 +28,10 @@ Table of contents:
27
28
28
29
This repository defines a Web application in the directory ` main ` and some auxiliary tools for testing and supporting a demo in the directory ` test ` .
29
30
30
- ## Getting Started
31
+ ## Getting started
31
32
32
- Go to directory ` main ` .
33
+ The application is located in directory ` main ` .
34
+ Go to that directory.
33
35
34
36
To install the application:
35
37
@@ -45,30 +47,35 @@ npm run dev
45
47
46
48
Now you can browse the displayed URL.
47
49
48
- The queries provided in the example configuration ` main/src/config.json ` access data located in pods at localhost.
49
- To have these up and running, you need to install the auxiliary tools first .
50
+ If you want to test the queries provided in the default configuration ` main/src/config.json ` ,
51
+ continue in section [ The supporting resources ] ( # the-supporting-resources ) .
50
52
51
- Go to directory ` test ` and execute:
53
+ ## The supporting resources
54
+
55
+ The supporting resources, including a local pod containing example data, are located in directory ` test ` .
56
+
57
+ To install, go to directory ` test ` and execute:
52
58
53
59
``` bash
54
60
npm install
55
61
```
56
62
57
- Next, also in directory ` test ` , activate the supporting resources:
63
+ Next, activate the supporting resources by executing each of the following steps
64
+ in a new terminal window, also in directory ` test ` :
58
65
59
- 1 . In a new terminal window, prepare and start the local pods:
66
+ 1 . Prepare and start the local pods:
60
67
61
68
``` bash
62
69
npm run reset:pods && npm run start:pods
63
70
```
64
71
65
- 2 . In a new terminal window, start the http proxy:
72
+ 2 . Start the http proxy:
66
73
67
74
``` bash
68
75
npm run start:proxy
69
76
```
70
77
71
- 3 . In a new terminal window, start a server which denies all CORS headers:
78
+ 3 . Start a server which denies all CORS headers:
72
79
73
80
``` bash
74
81
npm run start:badCors
@@ -87,7 +94,7 @@ In directory `main`, execute:
87
94
npm run build
88
95
```
89
96
90
- The static build appears in the ` dist ` folder .
97
+ The static build appears in directory ` main/ dist` .
91
98
92
99
## Logging in
93
100
@@ -336,25 +343,9 @@ The development version might be tested repeatedly during development.
336
343
npm run serve
337
344
```
338
345
339
- 2 . In a new terminal window, in directory ` test ` , prepare and start the local pods:
340
-
341
- ``` bash
342
- npm run reset:pods && npm run start:pods
343
- ```
344
-
345
- 3 . In a new terminal window, in directory ` test ` , start the http proxy:
346
-
347
- ``` bash
348
- npm run start:proxy
349
- ```
350
-
351
- 4 . In a new terminal window, in directory ` test ` , start a server which denies all CORS headers:
352
-
353
- ``` bash
354
- npm run start:badCors
355
- ```
346
+ 2 . Spin up all supporting resources, as explained in [ The supporting resources] ( #the-supporting-resources ) .
356
347
357
- 5 . Finally, in a new terminal window, in directory ` test ` , you can execute the tests by running:
348
+ 3 . Finally, in a new terminal window, in directory ` test ` , you can execute the tests by running:
358
349
359
350
For normal test execution:
360
351
0 commit comments