-
Notifications
You must be signed in to change notification settings - Fork 9
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
Grails Forge: in application.yml add environment specific database configuration #373
Comments
Is there anything stopping you from adding them, if your personal requirements benefit? |
One of the most striking features of Grails is that the application is already configured, I think that new programmers will have to research how to add configurations by environment, since it could already come by default, so it makes it easier. |
puneetbehl
referenced
this issue
Mar 7, 2024
This will add datasource config for each environments (development, test, and production). Fixes grails/grails-core#13103
jamesfredley
changed the title
In the application.yml file without environments settings
Grails Forge: In the application.yml file without environments settings
Sep 27, 2024
jamesfredley
changed the title
Grails Forge: In the application.yml file without environments settings
Grails Forge: in application.yml add environment specific database configuration
Oct 9, 2024
returning in 6.2.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
That the application.yml file came with the settings below
Actual Behaviour
When creating a project with grails 6.0.0 the application.yml file does not have the environments settings at the end as shown below
Steps To Reproduce
curl --location --request GET 'https://grailsforge-latest-cjmq3uyfcq-uc.a.run.app/create/web/com.example.demo?gorm=HIBERNATE&servlet=TOMCAT&test=SPOCK&javaVersion=JDK_11' --output demo.zip
unzip demo.zip
Environment Information
Grails Version: 6.0.0
Example Application
No response
Version
6.0.0
The text was updated successfully, but these errors were encountered: