7 | | 2. Execute the Scripts from Phase 2 in a PostgreSQL DB on the public schema(The Api and Scripts use the public schema) |
8 | | 3. Enter the connection string in appsettings.json in the API and your api should be good to go. |
9 | | - Please add Include Error Detail=True; at the end od the connection string so the errors we might have are more descriptive on the UI. |
| 7 | 2. if starting from an empty PostgreSQL database execute the Scripts from Phase 2 in a PostgreSQL DB on the public schema(The Api and Scripts use the public schema) |
| 8 | - For this project the scripts are **already executed** on the given DB so no need to execute them again. The App is ready to go. |
| 9 | |
| 10 | 3. Enter the connection string in appsettings.json in the API and your api should be good to go. |
| 11 | - Please add **Include Error Detail=True**; at the end od the connection string so the errors we might have are **more descriptive** on the UI. |
12 | | 5. Next open the UI Folder and Start the UI, execute npm install in the terminal. |
13 | | 6. Then find the app-settings.ts file in the UI |
14 | | - It should look like this, please change the port to the one shown in the browser of the swagger of the API |
| 14 | 5. Next open the UI Folder and Start the UI, execute** npm install** in the terminal. |
| 15 | 6. Then find the **app-settings.ts** file in the UI |
| 16 | - Please change the ApiUrl, change the port to the one shown in the browser of the swagger of the API |
| 17 | |
| 18 | {{{ |
| 19 | export enum AppSettings{ |
| 20 | ApiUrl = 'https://localhost:44306/api/', |
| 21 | OfflineMode = 0, |
| 22 | } |
| 23 | }}} |
| 24 | |