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
Copy file name to clipboardExpand all lines: ReadMe-Developer-Manual.md
+10-15Lines changed: 10 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,42 +20,37 @@ Now `npx` will now use the local `@nestjs/cli` version from `node_modules`.
20
20
21
21
## How to run in production
22
22
23
-
To start the application you need to create a `.production.env` file with the expected variables from `.sample.env`.
24
-
This file is not completely required, but the ENV variables from .sampe.env must be present in this environment.
25
-
26
-
If `.production.env` exists then the application will use the variables present there istead of those set globally in the `process.env`.
23
+
**Check if `.production.env` exists and it has the expected variables or if the environment variables from .sample.env are all set.**
27
24
28
25
```bash
29
26
$ nvm use #optional, but the min version of NodeJS should match the version from .nvmrc
30
27
$ nvm install(optional)
31
28
$ npm ci
32
-
$ npm run build:prod
33
-
$ # set NODE_ENV to production and execute npm run start:prod
29
+
$ npm run build
30
+
$ npm run start:prod
34
31
```
35
32
36
33
## How to run in dev
37
34
38
-
Same as production, but this time the file name must be `.development.test`
35
+
**Check if `.development.env` exists and it has the expected variables**
39
36
40
37
1. Switch to node verison >= the one mentioned in `.nvmrc`
41
38
2. Install the dependencies `npm ci` or `npm i`
42
39
3. Run in dev mode `npm run start:dev`
43
40
44
41
## How to run debug
45
42
46
-
Same as development
43
+
**Check if `.development.env` exists and it has the expected variables**
47
44
48
45
1. Open VSCode
49
46
2. All the settings are in `.vscode/launch.json`, so update them if you thing that is required
50
47
3. In `Run and Debug` panel, choose and run `Debug App`
51
48
52
-
## Test E2E
53
-
54
-
For E2E testing the workflow is the same as `development` or `production` in terms of system variables, but this time the file name must be `.test.env`.
55
-
56
49
## Other Scripts
57
50
58
51
`npm run test` - to run all the test files
59
-
`test:e2e` - to run only the E2E tests
60
-
`npm run lint` - to show linting warning or errors
61
-
`npm run lint:fix` - to lint and fix the code
52
+
`npm run lint` - to lint the code
53
+
54
+
# Data
55
+
56
+
The UAT data can be found in `data` folder in JSON format.
0 commit comments