Slow response time and 504 timeouts in Laravel Valet.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Looks like more and more users, including me, are having the same issue running Craft 3 with Laravel Valet. Seems like Craft 2 + other CMS are not having these issues. The developers over on the github issue-forum for Valet are pretty much out of ideas, so I was wondering if anyone has any input on this here? I absolutely love Valet, and I don't want to go back to MAMP or Homestead.
https://github.com/laravel/valet/issues/966
https://github.com/laravel/valet/issues/965
https://github.com/laravel/valet/issues/744
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names Craft 3 with Laravel Valet and links Valet issues 966, 965, and 744, but it names no Craft CMS file or test. Start by reviewing those linked reports and reproducing the timeout in the reported setup; done requires identifying a reproducible Craft-side cause and a scoped fix or confirmed upstream dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100