-
Notifications
You must be signed in to change notification settings - Fork 6
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
Improve naming of SSH key variable names #73
Comments
We currently have
(from documentation, automatically extracted from .env). I agree it's a bit cryptic (singular vs. plural keys). But I don't like long variable names, and we should not name the keys after what they are used for, but where they are installed. So how about …
…instead? |
From my side MANAGER_PUB_KEYFILE -> MANAGER_AUTHORIZED_KEYS, MANAGER_AUTHORIZED_KEYS_FILE Reasons |
I don't understand that.
it is the file to the public keys allowed on the Manager, so yes, the public part of the key that Kitodo is using would be part of that. Where's the problem?
And? |
I regularly get confused by the naming of the environment variables for SSH keys. For example, when I read
MANAGER_KEY
, I immediately assume that it's the key to access the manager when it's actually the manager's key to access the controller.Similarly, there are
MANAGER_KEYS
andCONTROLLER_KEYS
which I wouldn't know how to use either if it weren't for the explanatory comments next to them in the example.env
file.Therefore, I propose the following new names:
MANAGER_KEY
->MANAGER__CONTROLLER_ACCESS_KEY
MANAGER_KEYS
->MANAGER__AUTHORIZED_KEYS
CONTROLLER_KEYS
->CONTROLLER__AUTHORIZED_KEYS
Note that I included double underscores after the name of the service that the respective variables belong to. I find that it especially communicates the purpose of
MANAGER__CONTROLLER_ACCESS_KEY
more clearly that way.The text was updated successfully, but these errors were encountered: