Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mockery error in testing mode #118

Merged
merged 2 commits into from
Jan 29, 2024
Merged

Mockery error in testing mode #118

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
952b1af
mockery error in testing mode
ildyria Jan 29, 2024
6239bd5
Update docs/faq_troubleshooting.md
ildyria Jan 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/faq_installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
7 changes: 7 additions & 0 deletions docs/faq_troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
ildyria marked this conversation as resolved.
Show resolved Hide resolved

### 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.
Expand Down
Loading