Skip to content

Commit 96d19e4

Browse files
ildyriad7415
andauthored
Mockery error in testing mode (#118)
* mockery error in testing mode * Update docs/faq_troubleshooting.md Co-authored-by: Martin Stone <[email protected]> --------- Co-authored-by: Martin Stone <[email protected]>
1 parent 2e31c05 commit 96d19e4

File tree

2 files changed

+7
-2
lines changed

2 files changed

+7
-2
lines changed

docs/faq_installation.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,6 @@ However, if you want to be able to update your Lychee installation with a click
7474
As far as I know, the minimum set of directories that need to be http-writable is as follows:
7575
```
7676
storage/
77-
storage/
78-
storage/
7977
public/uploads/small
8078
public/uploads/big
8179
public/uploads/thumb

docs/faq_troubleshooting.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,13 @@ This will ensure that the paths and routes are correctly followed.
2626

2727
> {note} Note that the `serve` command should only be used for testing and debuging. It should not be used on a production server.
2828
29+
### I have an error 500, it says 'Class "Mockery" not found', what can I do?
30+
31+
This is because your `APP_ENV` is set to `testing` and you are using production dependencies.
32+
Lychee is trying to mock the requests for test purposes.
33+
34+
To resolve the issue, edit the `.env` file and set `APP_ENV` to something other than `testing`, for example `APP_ENV=production`.
35+
2936
### I have an error 500, what can I do?
3037

3138
Edit the `.env` file and set `APP_DEBUG` to `true`, this will allow the errors to be displayed with the trace.

0 commit comments

Comments
 (0)