You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you tremendously for continuing Cachet development :) I'd like to add a feature request, if you are open for it. I do miss a setting in .env or a configurable setting to support the chroot functionality of PHP-FPM.
FPM supports setting a custom chroot - but the CLI interpreter doesn't support this functionality. However, using CLI is required to install Cachet, to run artisan and it's the interpreter used with cron. This discrepancy between the two interpreters break the application.
Example:
Cachet lives in /var/www/cachet
The FPM chroot is set to /var/www
Running composer install and php artisan cachet:install puts the full path in bootstrap/cache/config.php
In this example, accessing Cachet from the webbrowser fires up FPM which tries to pull includes from /var/www/var/www/cachet/ - and thus throws an internal server error.
Proposed fix:
The ability to define the chroot in .env - in conjunction with detecting which interpreter is used (if that option is not set to null) gives Cachet the ability to run from chroot environments. In the above example, that prefix would be /var/www - which boils down to this path definition:
Thank you tremendously for continuing Cachet development :) I'd like to add a feature request, if you are open for it. I do miss a setting in
.env
or a configurable setting to support thechroot
functionality of PHP-FPM.FPM supports setting a custom
chroot
- but the CLI interpreter doesn't support this functionality. However, using CLI is required to install Cachet, to runartisan
and it's the interpreter used with cron. This discrepancy between the two interpreters break the application.Example:
/var/www/cachet
chroot
is set to/var/www
composer install
andphp artisan cachet:install
puts the full path inbootstrap/cache/config.php
In this example, accessing Cachet from the webbrowser fires up FPM which tries to pull includes from
/var/www/var/www/cachet/
- and thus throws an internal server error.Proposed fix:
The ability to define the
chroot
in.env
- in conjunction with detecting which interpreter is used (if that option is not set tonull
) gives Cachet the ability to run from chroot environments. In the above example, that prefix would be/var/www
- which boils down to this path definition:I hope this makes sense :)
The text was updated successfully, but these errors were encountered: