Sebastiaan Luca

Set up a push-to-deploy workflow to Vapor by using GitHub Actions.

When you first set up Highlight.js in a Turbolinks application, you might notice your code isn't highlighted anymore.

With the rise of active record and Laravel collections among other, many of us enjoy the possibility of fluently chaining method calls on an object. While this is being supported more and more, it requires implementation by the package or framework maintainer and is not possible for native values nor methods.

I recently came across a blog post that suggested using Composer's composer.json file to keep a reference to your most often used project-specific commands. I've been doing so for quite some time and it might be a matter of personal preference, but I find Yarn (or npm) to be better suited for this.

For those of us that use the terminal on a daily basis, sometimes even switching between projects throughout the day, it can be a quite repetitive and tedious task to have to open a terminal window, drill down to the correct project directory using cd, and then run some command to either boot your vagrant virtual machine or build your assets using webpack or gulp for example.