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
In development mode (i.e. when devMode = true, see Node configuration for more information), pre-configured keystores are used if the required keystores do not exist.
deployNodes is not able to set devMode
It seems like devMode is set to true by default as certificates are generated if they don't exist.
The documentation should be updated to more clearly reflect that.
It should also be documented to state whether deployNodes should be used for production builds or if it is purely for development purposes.
If it is for production you should be able to set devMode=false so unsafe certificates are not accidentally generated.
The text was updated successfully, but these errors were encountered:
I was just about to raise an issue about this when I found out I had already raised it 2 and a half years ago!
You still can't set devMode directly using the deployNodes task which is quite annoying when you want to quickly test your non-dev builds locally.
There is a workaround now though.
You can set it with extraConfig = ['devMode' : false]
There doesn't appear to be any particular reason why you have to use this workaround instead of just setting it directly though.
According to https://docs.corda.net/permissioning.html
deployNodes
is not able to setdevMode
It seems like
devMode
is set totrue
by default as certificates are generated if they don't exist.The documentation should be updated to more clearly reflect that.
It should also be documented to state whether
deployNodes
should be used for production builds or if it is purely for development purposes.If it is for production you should be able to set
devMode=false
so unsafe certificates are not accidentally generated.The text was updated successfully, but these errors were encountered: