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
Latest docs do not have any documentation on how to add JVM parameters to the CLI interface. If they do, I've been unable to find them with terms I'd expect to use.
Notably, words like memoryjvmsystem property should be included in the description, for searchability. I'd also recommend GRAILS_OPTS, as that was applicable for 2.3.x environments.
If it's no longer supported, that information should be accessible in the upgrading.
The closest I've found was searching for system properties, which yielded the page on run-app. I tested the server.port example and it did nothing. I attempted grails.server.port.http but that led to a cryptic error, which I'm not prepared to investigate.
The text was updated successfully, but these errors were encountered:
I'd also like to see the environments section (or some better place) of the docs contain a comprehensive listing of system environment variables that Grails pays attention to. ENV is a common way to pass configuration when deploying with docker. For example, is there a system environment variable that selects the grails environment that will be in effect? Something like GRAILS_ENV=dev or GRAILS_ENV=myTroubleshootingEnv.
for some reason (why introduce a breaking change like this?) -Dserver.port=xxxx is no longer supported, this sort of change needs proper documentation, the example of grails run-app -https implies that grails run-app -port=xxxx will work, but it does not.
Latest docs do not have any documentation on how to add JVM parameters to the CLI interface. If they do, I've been unable to find them with terms I'd expect to use.
Compare latest to 2.3.x.
Notably, words like
memory
jvm
system property
should be included in the description, for searchability. I'd also recommendGRAILS_OPTS
, as that was applicable for 2.3.x environments.If it's no longer supported, that information should be accessible in the upgrading.
The closest I've found was searching for system properties, which yielded the page on
run-app
. I tested theserver.port
example and it did nothing. I attemptedgrails.server.port.http
but that led to a cryptic error, which I'm not prepared to investigate.The text was updated successfully, but these errors were encountered: