From 2b1290dde7a3d2b633a1a6071fc9bcaf1531e0a2 Mon Sep 17 00:00:00 2001 From: Gauthier Roebroeck Date: Thu, 5 Mar 2020 21:01:16 +0800 Subject: [PATCH] docs: update DEVELOPING.md with profile changes --- DEVELOPING.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/DEVELOPING.md b/DEVELOPING.md index 04003df3..8c31bfee 100644 --- a/DEVELOPING.md +++ b/DEVELOPING.md @@ -19,11 +19,8 @@ Komga is composed of 2 projects: ### Spring profiles Komga uses Spring Profiles extensively: -- `dev`: add more logging, disable periodic scanning -- `prod`: log rotation, periodic scanning +- `dev`: add more logging, disable periodic scanning, in-memory database - `localdb`: a dev profile that stores the database in `./testdb`. -- `docker`: set default path for the docker image -- `flyway`: enable Flyway, the database migration tool. Included in `dev` and `prod`. - `noflyway`: disable Flyway. Only useful when adding new entities and you want Hibernate to update the database for you. - `generatesql`: used manually to write the SQL generated by Hibernate. Useful when adding new entities. @@ -39,7 +36,6 @@ Here is a list of useful tasks: `bootRun` needs to be run with a profile or list of profiles, usually: - `dev`: when testing with a blank database - `dev,localdb`: when testing with an existing database -- `prod`: when testing prod-specific features There are few ways you can run the task with a profile: - `./gradlew bootRun --args='--spring.profiles.active=dev'`