The log permission in laravel is inexplicably changed to root.

The framework uses laravel, which writes some data to the log and saves it to the storage directory. the file permission is automatically changed to the root permission after a while, as a result, laravel with only the www permission cannot be written into the log. Is this the case? Operation to log... the framework uses laravel, which writes some data to the log and saves it to the storage directory. the file permission is automatically changed to the root permission after a while, as a result, laravel with only the www permission cannot be written into the log. Is this the case?

Only one logstash is used to operate on log files. you can read visual logs on a regular basis.

Reply content:

The framework uses laravel, which writes some data to the log and saves it to the storage directory. the file permission is automatically changed to the root permission after a while, as a result, laravel with only the www permission cannot be written into the log. Is this the case?

Only one logstash is used to operate on log files. you can read visual logs on a regular basis.

You may have run the artisan command using the root command. for example, if you run a scheduled task as the root user, the root log file is generated.

chown -R www:www /path/to/laravel/storageIn this way, even the root user can read and write, and www can also read and write normally.

Scheduled task? yesrootThe

It should have been used.sudo php artisan xxx:xxxI have also met

Check whether php is run as Root.