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
League\Flysystem\Exception
Impossible to create the root directory "/var/task/resource/docs/1.0".
/tmp/vendor/league/flysystem/src/Adapter/Local.php:112
To Reproduce
Steps to reproduce the behavior:
We just wanted to install larecipe through the command line of vapor:
I guess this should already be done during the vapor deployment, because larecipe is part of the composer.json. But since that doesn't work we tried it manually and recived the exception above.
Please let me know if you need additional information. Thanks in advance!
Expected behavior
The install shoud be finished successfully and create the 'docs/1.0'-Folder where we could insert our markdown files (we retrieve them form google drive).
Desktop:
Laravel Vapor 2.9
Laravel Nova 3.16
Laravel 8
LaRecipe 2.4
Additional context
We're using Laravel Vapor for a serverless development. This error seems to only occure on the server side. It works on our localhost.
The text was updated successfully, but these errors were encountered:
Describe the bug
League\Flysystem\Exception
Impossible to create the root directory "/var/task/resource/docs/1.0".
/tmp/vendor/league/flysystem/src/Adapter/Local.php:112
To Reproduce
Steps to reproduce the behavior:
We just wanted to install larecipe through the command line of vapor:
I guess this should already be done during the vapor deployment, because larecipe is part of the
composer.json
. But since that doesn't work we tried it manually and recived the exception above.Please let me know if you need additional information. Thanks in advance!
Expected behavior
The install shoud be finished successfully and create the 'docs/1.0'-Folder where we could insert our markdown files (we retrieve them form google drive).
Desktop:
Additional context
We're using Laravel Vapor for a serverless development. This error seems to only occure on the server side. It works on our localhost.
The text was updated successfully, but these errors were encountered: