Improve readme and add warning on rails credentials conflict #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julik
approved these changes
Jun 11, 2024
svanhesteren
force-pushed
the
improve-readme
branch
from
af8c2ae
to
a61b8b6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Eyaml doesn't work with the new rails' credentials encryption (they both do the same thing in principle). The rails credentials management relies on a
.yml.encfile which is encrypted via a key present in the master.key file (which is 32 bytes). Eyaml uses it own key which is 64 bytes in fact. I've improved the readme for general eyaml config/installation and added a raise when a master/key file is present.