Conversation
|
The only issue I've noticed so far is that if I dont set the ENVs I added I get an error about invalid values. So if someone could direct me on how to fix that I'll do it (or I'll investigate later) |
|
Thanks for this PR!
I am not sure about the issue. Where do you see these errors? Can you provide the stacktrace? |
|
Would you mind adding tests for the additions you made? |
|
@all-contributors add @tm1000 for code |
|
I've put up a pull request to add @tm1000! 🎉 |
When using docker (I rebuilt until this makes it in your release) |
…ote-cache into feature/fixes-32-62
|
So I just rebuilt the container and I omitted BODY_LIMIT. It's marked as Optional in the env file but still throws this error unless I define it so I must be missing something |
|
Maybe for some reason it defaults to empty string? 🤔 |
That was it. Its because of the remapping happening inside of the Dockerfile. There's no need to set ENVs back to themselves as this is done automatically in docker itself when running the container so there is no point in setting empty values when building. When you end up setting booleans to undefined then it becomes a string and then it doesn't validate. I fixed this in ea614b3 and rebuilt my container and now it works without the values defined |
|
@fox1t I can write some tests if you think the code is good to go now |
|
I think that now everything seems in place! Waiting for some tests to merge this! |
|
@fox1t I'm still working on tests if you want them! Sorry for the delay! |
This fixes #32 and #62