-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to parse application-prod.yml in JHipster 6.10 fat jar #244
Comments
Can you try downgrading your driver as described in #234 and let me know if it helped? |
yes, downgraded the driver. thanks! Does boxfuse work with latest stable release of jhipster with postgresql? Am i missing something? |
What is the root exception you are seeing in that stacktrace in your prod environment? |
Ok, the problem was that fusebox doesnt parse application-prod.yml if it is packaged in jar mode. Jhipsters boxfuse documentation page has a mistake, should be updated with the following command: ./gradlew -Pprod -Pwar clean bootWar if war is generated, the yml is parsed, and the securityconfig is built. Now everything looks and works fine. thanks! |
Thanks for the thumbs up. I've updated the issue title to reflect this. Which version of JHipster are you using exactly? |
6.10.5 |
Hello,
Currently if i run my Jhipster app on virtualbox i get: PSQLException: The hostname 10.0.2.2 could not be verified by hostnameverifier PgjdbcHostnameVerifier. (it works good on normal springboot startup ofc)
Running on AWS: PSQLException: Could not open SSL root certificate file //.postgresql/root.crt.
Question is: Am i missing something, or the jdbc url should be manipulated in a different way by boxfuse.
Seems like boxfuse ignores the get parameters like: sslmode=verify-ca inside it.
Locally on virtualbox: postgresql://10.0.2.2:5433/boxfuse-dev-db?ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory
On AWS deploy:
-DSPRING_DATASOURCE_URL=jdbc:postgresql://xxxx-xxxx-xxxx-xxxx:5432/xxx_xxx?ssl=true'
no matter if i change something in my application-prod.yml
The text was updated successfully, but these errors were encountered: