fix: add SECRET as env variable to docker-compose setup #298
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 might close #284
Description
The
SECRET
env variable is mandatory by now, but the README and thedocker-compose.yml
don't reflect this.People running the service as docker will run into the following error:
web-socket-adapter: unable to handle message: Error: SECRET environment variable not set
This can be fixed setting up a secret and providing it via a
.env
file in thedocker-compose.yml
.Related Issue
#284
Motivation and Context
see description
How Has This Been Tested?
I tested it with my own relay.
Before I was not able to send events. I did get no error message, but no success or "OK" response as well.
Now I am.
Screenshots (if appropriate):
Types of changes
Checklist: