[
https://issues.apache.org/jira/browse/FINERACT-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615968#comment-17615968
]
Aleksandar Vidakovic commented on FINERACT-1763:
------------------------------------------------
Note to self:
* apply same strategy for "bootRun" with custom modules as with custom Docker
images... create a Spring Boot application project under "custom" folder that
(dynamically) references all custom modules and run that with "bootRun"...
should be fairly easy
* prepare a Docker Compose file with default database configuration needed by
Fineract
* provide an easy way to configure minimum set of env vars to be able to
launch locally (provide an external "application-local.properties" in the root
folder, not managed by VCS, used by bootRun to override defaults)
> Enable developers to run Fineract with bootRun
> ----------------------------------------------
>
> Key: FINERACT-1763
> URL: https://issues.apache.org/jira/browse/FINERACT-1763
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Aleksandar Vidakovic
> Assignee: Aleksandar Vidakovic
> Priority: Major
> Fix For: 1.9.0
>
>
> Various community members requested to be able to run Fineract with a simple
> "bootRun" Gradle task on their machines. This would facilitate debugging and
> ensure faster turnarounds. Actually, we could even support Spring Boot's
> hotreload during development (automatic reload on file save).
> The current way to run a debug session is to recreate a Docker image (with
> JVM debug parameter in the command line) and do remote debugging with the IDE.
> Bonus: find a configuration that allows "bootRun" to include custom modules
> without changing any of "fineract-provider"'s dependencies (our core services
> should not be aware of any customizations).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
