Thread tagged as: Problem, Hosting

Serving Perch with Laravel Valet again

Previous thread but this is a different problem.

On macOS High Sierra 10.13.6, with a new installation of Valet 2.0.12, when trying to set up a new Perch 3.1.2 site, Perch redirects site.test/perch to site.test/setup and I get a Valet 404. PHP version is 7.2.8.

Isn't it meant to redirect to site.test/perch/setup?

Nothing is logged in ~/.valet/Log.

Is anyone else experiencing this?

This is my first time trying Perch with Valet.

Lief van der Baan

Lief van der Baan 0 points

  • 3 years ago
Drew McLellan

Drew McLellan 2638 points
Perch Support

Isn't it meant to redirect to site.test/perch/setup

Yes, that's what it's meant to do.

With so many different ways of running a web server, we can't provide one on one support for every possible combination, but someone else here might be familiar with Valet enough to help out.

Drew, I understand. No worries :)

I'm looking into it. I'll leave notes here for posterity.

Not having much knowledge of much yet, I'm only guessing that somewhere in Valet, the Location header directives in perch/index.php, perch/setup/index.php, etc. down the route to perch/setup/server are being misinterpreted as starting at the root URI, rather than being relative. Where in the request line that could be happening, I'm not sure yet.

I'll get back to this post once I've come up with more than that. I'm not sure if I should be writing a custom Valet driver or a custom Nginx configuration yet.