Events-WebAPI fix and tweak

This commit is contained in:
Boris Milašinović
2026-05-12 17:23:45 +02:00
parent b66d05c298
commit 3f2e199ec4
12 changed files with 209 additions and 10 deletions

View File

@@ -159,6 +159,35 @@ Once the APIs are running:
- most `WebAPI` endpoints require a bearer token
- `FilesAPI` download endpoints are also protected and require the `events:read` scope
## Running Everything Without VS Code
From the `Events-WebApi` directory, you can start all three processes together with:
```bash
./start-all.sh
```
This starts:
- `Events.WebAPI` on `https://localhost:7295`
- `Events.FilesAPI` on `https://localhost:7296`
- `Events.ClientApp` on `http://localhost:5173`
The script keeps all processes attached to the terminal and stops them together when you press `Ctrl+C`.
If you want to stop the stack from another terminal, use:
```bash
./stop-all.sh
```
Before the first run, make sure the client dependencies are installed:
```bash
cd Events.ClientApp
npm install
```
## Running The Client App
See [Events.ClientApp/README.md](/C:/GitRepos/FPMOZ-PI/predavanja/Events-WebApi/Events.ClientApp/README.md:1) for more details.
@@ -180,7 +209,7 @@ npm run dev
According to the current `appsettings.json`, the default is:
```text
./Certificates
./GeneratedFiles
```
## Troubleshooting