-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search for ray.php triggers warning if open_basedir restrictions are in place and ray.php is not found beneath allowed directories #73
Comments
This will be fixed in v1.3.4 of the package. |
For me this is still an issue with v1.5.6. I get this error: |
This is hard to fix without a stack trace. Also, I don't have an environment where this option is set to true. I'd appreciate you opening a new issue for this with as much detail as you can. |
I've fixed this now by creating a
This prevents the |
That's nice way to go about it 👍 |
Describe the bug
If open_basedir restrictions are in effect and Ray does not find a
ray.php
in allowed directories, it'll keep "digging up" until itsis_dir()
call is made on a forbidden directory. In my case, it goes above/srv/www
to callis_dir('/srv')
which triggers this warning:Versions
Ray version (you can see this in "About Ray"):
1.3.2 (spatie/ray)
PHP version:
7.4.6
Laravel version (if applicable):
Not using Laravel.
To Reproduce
ray.php
under that directoryray()
Expected behavior
No warnings.
ray.php
is optional according to the documentation.The text was updated successfully, but these errors were encountered: