You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, my experience with gradle is fairly basic. I'm not familiar with the nuances of having multiple subprojects in on repo.
I'm starting with the semantic-search example, and stumbled upon this gradle command to start that "subproject" from the repo 'root' folder: ./gradlew :use-cases:semantic-search:bootTestRun
which seems to correctly use a testContainer for postgres (with pgvector enabled). I do also have a non-containerized postgres service running by default, but stopped it while working on understanding the demo apps (and using testContainers)
The command in the readme : ./gradlew bootTestRun
fails in the semantic-search folder because there is no ./gradlew.
Perhaps I am lacking some basic/implied understanding of gradle/gradlew?
This is more of checking my sanity/understanding rather than an actual problem or issue. Is this 'best practice' or is there a better approach I should take?
Second: I notice the application.yml for each subproject does not have datasource settings. This again is likely me having missed something basic/implied in the configuration. Should I be adding something like the following to each of the sub application.yml files?
Hi, my experience with gradle is fairly basic. I'm not familiar with the nuances of having multiple subprojects in on repo.
I'm starting with the semantic-search example, and stumbled upon this gradle command to start that "subproject" from the repo 'root' folder:
./gradlew :use-cases:semantic-search:bootTestRun
which seems to correctly use a testContainer for postgres (with pgvector enabled). I do also have a non-containerized postgres service running by default, but stopped it while working on understanding the demo apps (and using testContainers)
The command in the readme :
./gradlew bootTestRun
fails in the semantic-search folder because there is no ./gradlew.
Perhaps I am lacking some basic/implied understanding of gradle/gradlew?
This is more of checking my sanity/understanding rather than an actual problem or issue. Is this 'best practice' or is there a better approach I should take?
Second: I notice the application.yml for each subproject does not have datasource settings. This again is likely me having missed something basic/implied in the configuration. Should I be adding something like the following to each of the sub application.yml files?
In any event, thanks for publishing this repo with great examples. These are a huge help!
The text was updated successfully, but these errors were encountered: