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

TLS key configuration doesn't have useful default when using a non-default rootdir #1321

Closed
orpheuslummis opened this issue Apr 11, 2023 · 0 comments · Fixed by #1318
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@orpheuslummis
Copy link
Contributor

It would be useful to have the certs loaded if they're in a conventional place.
A solution is to have, by default, the paths relative to the "DefraDB root directory", in this case the defaults would be e.g. pubkeypath=certs/secret.crt, privkeypath=certs/secret.key and rootdir=~/.defradb. In addition, having the convention of using DefraDB-relevant data of single default DefraDB install be in one folder by default allows some simplicity.

@orpheuslummis orpheuslummis added the bug Something isn't working label Apr 11, 2023
@orpheuslummis orpheuslummis added this to the DefraDB v0.5 milestone Apr 11, 2023
@orpheuslummis orpheuslummis self-assigned this Apr 11, 2023
orpheuslummis added a commit that referenced this issue Apr 11, 2023
Resolves #1321
Resolves #1319
Resolves #1317
Resolves #1316
Resolves #1315
shahzadlone pushed a commit that referenced this issue Apr 13, 2023
Resolves #1321
Resolves #1319
Resolves #1317
Resolves #1316
Resolves #1315
shahzadlone pushed a commit to shahzadlone/defradb that referenced this issue Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant