Closed michzimny closed 6 years ago
Hi @michzimny, if you need help with setting these variables maybe we can also give a hand.
Hi @Alfro, you're right that it might be the case with having right values of the config variables. I would prefer though that @athird or @Tabbasum take this and check the values with you if needed.
I'm not experiencing this issue anymore. I think it could have been caused by #92.
When deploying to production (
./deploy.sh production 49c2b66d6d1e34c3c3f0bedf888098ef075eb0c6
), the script ends up with the following output:I don't know if that matters but maybe something gets improperly configured. Maybe there's an issue with the quote marks in *.env files? I don't now which approach to quote marks is the right one as we have various of them in the env repo :-)