One of the nice things of Laravel Valet is that it includes an easy way to make your local site available publicly. For this it has the aforementioned Ngrok built-in. To use it, just run the valet share command, and your local site will be shared through a *.ngrok.io subdomain.
However, when combining valet share with valet secure(which serves your local site over HTTPS) it won’t work: you’ll end up in a 301 Redirect Loop when visiting your site through the *.ngrok.io domain.
To fix this issue there are two options:
The old way: Manually edit your sites Nginx config file and remove the block that listens on port 80.
As valet issue#382 details, you can fix this error by manually editing the Nginx configuration for your site.
Say your site is mysite.test, then its Nginx config file can be found at ~/.config/valet/Nginx/mysite.test.
Earlier today I updated my Valet installation from version 2.0.x to 2.1.1. To my surprise the ~/.valet/ folder had gone missing, immediately making me think the update process somehow had gone wrong (even though Valet kept on serving sites).
Turns out that the ~/.valet/ folder got moved to ~/.config/valet/ with the release of Valet 2.1.0.
So yes, the valet logs are now located in ~/.config/valet/Log/ instead of ~/.valet/Log.
/me mumbles something about semver and breaking changes and stuff …
Did this help you out? Like what you see? Consider donating.
About two years ago I started watching Star Wars with my children. Whilst watching the first movie (Episode IV) I kind of found Darth’s role quite disturbing. He was just floating there in the background, and all stuff that we associate with him wasn’t that well expressed. It’s only during Episode V that his character is presented as how I remember it.
Swoole is an high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient. It is written in C language without 3rd party libraries as PHP extension.
It enables PHP developers to write high-performance, scalable, concurrent TCP, UDP, Unix Socket, HTTP, WebSocket services in PHP programming language without too much knowledge about non-blocking I/O programming and low-level Linux kernel.
Compared with other async programming frameworks or softwares such as Nginx, Tornado, Node.js, Swoole has the built-in async, multiple threads I/O modules. Developers can use sync or async API to write the applications.
Will be checking this one out, as an alternative to ReactPHP, since this one comes as a PECL extension. Speed should be heavily better. A quick search around tells me it performs quite well indeed.
🤓 Back in 2006 (!) I created a small site/tool named “The Box Office” to fake that. It took the line-height and floated a truckload of boxes to one side to fake the effect. It’s been long discontinued by now.
If you’re using React Navigation in your app(s) you might have noticed these two issues the folks over at November Five have written about:
On a few screens – specifically those with lots of components – we started noticing a few things…
Right off the bat, there is a substantial delay between the user pressing a button and the swipe-in animation of a new screen. When a new screen is pushed, React Navigation will initially render it off-screen and animate it into place afterwards. This means that when a complex screen with lots of components that easily takes a few hundred milliseconds to render is pushed, it feels less snappy than a natively written application. It also causes some nasty side effects: for instance, if you tap a button quickly, you can trigger the same route from being pushed multiple times.
Another problem is that business logic can be executed while the swipe-in animation is doing its thing. This can make for a janky animation.
Of course the post also contains fixes for these problems 😉