Clarify .env quoting and add dotenv-linter recommendation #113
+38
−0
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 is an update to the project Readme.md that handles properly quoting special characters and offers a way to cleanup a broken docker compose that has a malformed .env vs /home/node/.n8n/config from the n8n volume.
Note
Clarifies quoting special characters in
.env, adds troubleshooting cleanup/redeploy steps, and recommendsdotenv-linter..envto avoid parsing issues.password,N8N_ENCRYPTION_KEY, andN8N_USER_MANAGEMENT_JWT_SECRETin quotes./home/node/.n8n/configmessage.dotenv-linterto validate env files.docker compose down --volumes --remove-orphans, remove volumes (n8n_storage,postgres_storage,ollama_storage,qdrant_storage), optionally remove images, and verify withdocker ps -aanddocker volume lsbefore redeploying.Written by Cursor Bugbot for commit e4ba044. This will update automatically on new commits. Configure here.