Fix n8n persistant dir #1197
Merged
Fix n8n persistant dir #1197
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
This fixes the persistant directory, which is wrong initially This is especially anoying because if you fix the path after having used n8n for a while it messes up the ecryption key of all your services (credentials, apis etc) which resets all your integrations
lexoyo
force-pushed
the
fix_n8n-persistant-dir
branch
from
5dfde3d to
d046ad1
Compare
|
Thanks!! |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This fixes the persistant directory, which is wrong initially
This is especially anoying because if you fix the path after having used n8n for a while it messes up the ecryption key of all your services (credentials, apis etc) which resets all your integrations