Tag: Laravel

All the articles with the tag "Laravel".

• SonarQube

  6 Aug, 2022

  Code quality and code security https://www.sonarqube.org I found this very useful in scanning my code and pointing out some basic quality and security impr

• Components, props and emit events

  6 Aug, 2022

  One of the things that trips me up is writing Vue components and passing in parameters and returning results. It's a one way process in the main. You can p

• Laravel and Vue.js

  Updated:21 Jun, 2022

  I tried to pick up where I left off with my Laravel skills. I began with some vuejs pages and wrote the api to feed the data to them using axios. It took m

• Laravel Jetstream and OpenLDAP

  Updated:24 May, 2022

  It's been a very long time since I did anything with Laravel. I found another job around the time of Laravel 6, and today they are up to Laravel 9 - much h

• Relearning Laravel

  24 May, 2022

  I feel like the past few days have been quite a battle. Mostly in terms of my memory and trying to remember what I did with Laravel and how I can re-establ

• JWTAuth, Laravel and Vue.js

  Updated:22 Mar, 2021

  The past few days have been rather eventful trying to get JavaScript Web Tokens (JWT) to authenticate my Laravel, Vue.js environment. As per my previous po

• Laravel, Nuxt.js and Nginx

  2 Oct, 2019

  Whilst experimenting with Nuxt.js (A Vue.js framework) as a front end client for Laravel I discovered I was going to face some issues with CORS, certificat

• Laravel and Firebase Sync

  Updated:30 Sep, 2019

  Today I've been working on an idea I've had for a while now. Sometimes you want your internal data exposed to the outside world, but don't really want to o

• Laravel and O365 Authentication

  Updated:4 Sep, 2019

  Our app currently uses LDAP authentication but as our environment is rapidly moving onto the cloud and Microsoft Office 365 it's time to investigate authen

• PHPUnit Testing Failure

  Updated:20 Aug, 2019

  Today's challenge caused me to burn a lot of time before resolving the issue, which turned out to be an obvious mistake. When I run a unit test I need to a