Replies: 1 comment
-
Figured out what was happening. I had created my own config/ray.php file for other uses, and that file is overwriting in the ray.php file in the root. After renaming my own custom ray.php file to something else the overwrite stopped happening and the values in my .env file are now being honoured |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm really confused, I'm using Ray in production on several servers, on all of them except one it just works.
I have a test command in which I have both
ray()->enable()
and then I check if it's enabled usingray()->enabled()
and it returns true. In my config file I also haveRAY_ENABLED=true
The latest ray / laravel-ray is installed, and it works fine on dev, but on production it just quietly fails to output anything, whereas on other servers it works.
Normally is having the config file in the root, and having
RAY_ENABLED=true
in your .env file enough to force ray to work in production? Or is there something more that's needed?Beta Was this translation helpful? Give feedback.
All reactions