Backup_Repos/komga
1
0
Fork 0
mirror of https://github.com/gotson/komga.git synced 2026-05-05 02:53:09 +02:00
Code Issues Projects Releases Wiki Activity

docs: clarify CORS usage for frontend dev

Browse source
This commit is contained in:
Gauthier Roebroeck 2021-12-03 09:12:42 +08:00
parent 5772562db6
commit 0e1c6388a4
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
DEVELOPING.md
View file

@ -26,7 +26,7 @@ Komga is composed of 2 projects:
### Spring profiles
Komga uses Spring Profiles extensively:
- `dev`: add more logging, disable periodic scanning, in-memory database
- `dev`: add more logging, disable periodic scanning, in-memory database, and enable CORS from `localhost:8081` (the frontend dev server)
- `localdb`: a dev profile that stores the database in `./localdb`.
- `noclaim`: will create initial users at startup if none exist and output users and passwords in the standard output
- if `dev` is active, will create `admin@example.org` with password `admin`, and `user@example.org` with password `user`
@ -60,3 +60,4 @@ SET SPRING_PROFILES_ACTIVE=dev
You can run a live development server with `npm run serve` from `/komga-webui`. The dev server will override the URL to connect to `localhost:8080`, so you can also run `gradle bootRun` to have a backend running, serving the API requests. The frontend will be loaded from `localhost:8081`.
Make sure you start the backend with the `dev` profile, else the frontend requests will be denied because of CORS.