Bugfix/Change encryption key path #1418
Merged
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
hemati
pushed a commit
to hemati/Flowise
that referenced
this pull request
Dec 27, 2023
…crypt Bugfix/Change encryption key path
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.
When doing
npm install -g flowise, thennpx flowise start, the default path forencryption.keyis created within the Flowise folder.Problem arises when user upgrade flowise by running
npm install -g flowise. This will remove all the files includingencryption.keyand recreate a new one.Fix: change the default path to be user home
.flowise, the same place wheredatabase.sqliteis located