From 952b1af18d583c824e69027a7aaae7c986a84157 Mon Sep 17 00:00:00 2001 From: ildyria Date: Mon, 29 Jan 2024 11:26:34 +0100 Subject: [PATCH] mockery error in testing mode --- docs/faq_installation.md | 2 -- docs/faq_troubleshooting.md | 7 +++++++ 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/faq_installation.md b/docs/faq_installation.md index 420102a3..173c8388 100644 --- a/docs/faq_installation.md +++ b/docs/faq_installation.md @@ -74,8 +74,6 @@ However, if you want to be able to update your Lychee installation with a click As far as I know, the minimum set of directories that need to be http-writable is as follows: ``` storage/ -storage/ -storage/ public/uploads/small public/uploads/big public/uploads/thumb diff --git a/docs/faq_troubleshooting.md b/docs/faq_troubleshooting.md index 5aec1dd4..20ecda02 100644 --- a/docs/faq_troubleshooting.md +++ b/docs/faq_troubleshooting.md @@ -26,6 +26,13 @@ This will ensure that the paths and routes are correctly followed. > {note} Note that the `serve` command should only be used for testing and debuging. It should not be used on a production server. +### I have an error 500, it says 'Class "Mockery" not found', what can I do? + +This is because your `APP_ENV` is set to `testing` and you are using production dependencies. +Lychee is trying to mock the requests for test purposes. + +To resolve the issue, edit the `.env` file and set `APP_ENV` to something else than `testing`, for example `APP_ENV=production`. + ### I have an error 500, what can I do? Edit the `.env` file and set `APP_DEBUG` to `true`, this will allow the errors to be displayed with the trace.