We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description In the absense of jwt-secret file and a change in default data directory, jwt-secret file is still generated in default data directory.
Note: check for similar behaviour if data directory is specified using env or config file.
Steps to Reproduce In order to replicate the behavior, please provide a detailed list of steps:
--dd <new_data_dir>
Actual behavior jwt-secret file is generated in src/Nethermind/Nethermind.Runner/keystore.
src/Nethermind/Nethermind.Runner/keystore.
Expected behavior jwt-secret file should be generated in <new_data_dir>/keystore
<new_data_dir>/keystore
The text was updated successfully, but these errors were encountered:
Hey @obasekiosa , can you check if the linked PR addresses the issue.
Sorry, something went wrong.
Can I take care of this issue?
May I take this issue on?
Can I take this from here?
Successfully merging a pull request may close this issue.
Description
In the absense of jwt-secret file and a change in default data directory, jwt-secret file is still generated in default data directory.
Note:
check for similar behaviour if data directory is specified using env or config file.
Steps to Reproduce
In order to replicate the behavior, please provide a detailed list of steps:
--dd <new_data_dir>
Actual behavior
jwt-secret file is generated in
src/Nethermind/Nethermind.Runner/keystore.
Expected behavior
jwt-secret file should be generated in
<new_data_dir>/keystore
The text was updated successfully, but these errors were encountered: