Skip to main content

Laravelnote: Tinkerwell now with Apple Silicon support in laravel8

 Tinkerwell, the desktop app that allows you to run PHP code and quickly try out new ideas, has launched a new version that supports Apple Silicon and includes a lot of other great features. Some of the highlights of this release include:

Laravelnote | Real-time code output 

Previous versions of Tinkerwell always buffered the output and then showed you the evaluated result at once. With version 2.13 of Tinkerwell, this is no longer the case. Tinkerwell shows you the output of your PHP code in real-time, as it occurs. In addition to this, you can now also stop long-running PHP processes by clicking the "Run" button again and have a "loading" indicator in the toolbar so that you always know the state of the current code evaluation.

Laravelnote| Improved SSH connection manager

The Tinkerwell SSH connection manager got a completely new design in this version together with some great new features. This new connection manager allows you to sort and group your SSH connections. This is useful if you have the same site on different environments, for example, staging and production.

In addition to grouping and sorting, you can now also color-code your SSH connections. Do you want to emphasize that a connection is in production? Why not give it a red color code.

When you open up an SSH connection, you will now also see the color code within the tab bar, so you always know which connection you are currently working with.

New Shortcut | Laravelnote

They added a new shortcut that allows you to toggle the auto code evaluation mode. Press CMD/Ctrl+Shift+A to toggle between automatically evaluating your code as you type it, or manually running it using CMD/Ctrl+R or by pressing the "Run" button in the toolbar.

For more information, check out the Tinkerwell website to read more. Since its original launch, I've been using Tinkerwell, and it's now an app I use constantly. Highly recommend it!

Labels:

Popular posts from this blog

Create Your Next Project's Readme in Laravel8 | laravelnote

  The readme.so editor gives you visual cues, starter section templates and includes many standard readme sections you're likely to use. It also has a nice preview to help guide you along the way. Never forget a section for your readme again! Select sections to add to your readme, edit the contents, and drag to rearrange. See a live-updating rendered preview of your markdown, then download your README.md file! Here's an example of starting an API section, which provides helpful formatting. You might need to specify API params: The editor includes both light and dark editor support, and you can download or copy/paste the raw markdown of your readme into version control once you're done. You can learn more about this project and start using it on  readme.so . Also, be sure to check out  readme.so on Product Hunt  and upvote it if you find it useful!
Read more

Laravel8 in Serializes Models trait | laravelnote

This article was originally posted, with additional formatting, on my personal blog at laravel serializes model Background  When dispatching an object onto the queue, behind the scenes Laravel is recursively serializing the object and all of its properties into a string representation that is then written to the queue. There it awaits a queue worker to retrieve it from the queue and unserialize it back into a PHP object (Phew!). Problem When complicated objects are serialized, their string representations can be atrociously long, taking up unnecessary resources both on the queue and application servers. Solution Because of this, Laravel offers a trait called SerializesModels which, when added to an object, finds any properties of type Model or Eloquent\Collection during serialization and replaces them with a plain-old-PHP-object (POPO) known as a ModelIdentifier. These identifier objects represent the original properties Model type and ID, or IDs in the case of an Eloquent\Collecti...
Read more

Check if a Laravel request is from the CLI on Laravelnote

  There might be times where you need to know if a request to your Laravel app is coming from the CLI or from the web. As an example, I wanted to turn on the   query log   to dump out all the SQL queries. In AppServiceProvider I added a simple config check to turn on the the log: if (config('settings.profile')) { \DB::connection()->enableQueryLog(); } With this in place, it would run for web requests, as I wanted, but the side effect is it would also be turned on in our queue jobs and other CLI tasks. Laravel runningInConsole | Laravelnote Laravel provides a simple helper called  runningInConsole  that you can use to help determine what environment you are in. app()->runningInConsole() With this I could just an inverse check to make sure my code only runs when it's a web request: if (config('settings.profile') && ! app()->runningInConsole()) { \DB::connection()->enableQueryLog(); } If you ever come to a situation where you need to know w...
Read more