Skip to content
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

Can't Set devMode From deployNodes #31

Open
opticyclic opened this issue Mar 12, 2018 · 1 comment
Open

Can't Set devMode From deployNodes #31

opticyclic opened this issue Mar 12, 2018 · 1 comment

Comments

@opticyclic
Copy link

According to https://docs.corda.net/permissioning.html

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.

@opticyclic
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant