Add initial project structure with Maven, Quarkus, and React setup
- Created .gitignore to exclude build artifacts and IDE files. - Added pom.xml for Maven project configuration, including dependencies for Quarkus, OpenAPI, and testing. - Introduced project documentation outlining development workflow, architecture, and coding standards. - Implemented core business logic with services for authentication, scenario management, story lifecycle, and user management. - Established security context for JWT-based authentication. - Generated API specifications and client code for frontend integration. - Set up initial database entities and repositories for user, scenario, and story management.
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
quarkus.http.port=8080
|
||||
quarkus.http.cors=true
|
||||
|
||||
quarkus.liquibase.migrate-at-start=true
|
||||
quarkus.liquibase.change-log=db/migration/db.changelog-master.yaml
|
||||
|
||||
quarkus.datasource.db-kind=postgresql
|
||||
quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/storyteller
|
||||
quarkus.datasource.username=storyteller
|
||||
quarkus.datasource.password=storyteller
|
||||
|
||||
quarkus.hibernate-orm.database.generation=none
|
||||
|
||||
mp.jwt.verify.publickey.location=publicKey.pem
|
||||
mp.jwt.verify.issuer=storyteller
|
||||
smallrye.jwt.sign.key.location=privateKey.pem
|
||||
smallrye.jwt.new-token.lifespan=86400
|
||||
smallrye.jwt.new-token.issuer=storyteller
|
||||
|
||||
quarkus.http.auth.permission.public.paths=/api/auth/*
|
||||
quarkus.http.auth.permission.public.policy=permit
|
||||
quarkus.http.auth.permission.protected.paths=/api/*
|
||||
quarkus.http.auth.permission.protected.policy=authenticated
|
||||
quarkus.http.auth.permission.static.paths=/*
|
||||
quarkus.http.auth.permission.static.policy=permit
|
||||
Reference in New Issue
Block a user