Debugging AWS SAM

This took a few to get just right, for one the command needs to be in the correct order sam local invoke --event fixtures/latest_not_working.json -d 5858 GithubPushes From here it gave me the output I was looking for: sam local invoke --event fixtures/latest_not_working.json -d 5858 GithubPushes 2018/05/07 06:49:46 Successfully parsed template.yaml 2018/05/07 06:49:46 Connected to Docker 1.37 2018/05/07 06:49:46 Fetching lambci/lambda:nodejs8.10 image for nodejs8.10 runtime... nodejs8.10: Pulling from lambci/lambda Digest: sha256:a53fceb64e2339332dbc4117be8ec270f46fbe28d564499f1cf73035a1c5854e Status: Image is up to date for lambci/lambda:nodejs8.

May 7, 2018 Read
wip Fargate and Laravel

……

April 11, 2018 Read
Getting Started with Orchestra Testbench for Laravel Package Development

The goal of this article will allow one to setup a stand alone package working with it’s own tests and has access to all of the normal Laravel workflows outside of Laravel. So you can build it using the easier conventions and helpers Laravel offers. Since my work will include database usage I will grab both packages: composer require --dev "orchestra/testbench:<=3.5" "orchestra/database:v3.5.0" I will setup my composer.json after this as such:

April 1, 2018 Read
BrowserSync and Laravel

Quick reminder to take advantage of this amazing feature https://laravel.com/docs/5.6/mix#browsersync-reloading No more reloading your browser. yarn add browser-sync --dev then to your webpack.mix.js e.g. the domain of the site you are working on. mix.browserSync('foo.test'); finally yarn run watch Note turn off sourceMaps when running this else it can be kinda slow

March 15, 2018 Read
GroupBy not Sorting by latest

Just to make this easy to find. I had a report to write which had numerous daily rows of the same related model data. So in this cause I was tracking servers and security reports. My reports where daily like this id server_id failed type 1 1 1 security 2 1 1 testing 3 1 0 testing But a groupBy here on server_id would return ID 1 so it would appear as if it was still failing.

March 15, 2018 Read
Troubleshoot Laravel Socialite and Github login

This has driven me mad too many times. Basically you will get very little feedback if there is any issue getting the token from Github. The problem is in this method. public function user() { if ($this->hasInvalidState()) { throw new InvalidStateException; } $response = $this->getAccessTokenResponse($this->getCode()); $user = $this->mapUserToObject($this->getUserByToken( $token = Arr::get($response, 'access_token') )); return $user->setToken($token) ->setRefreshToken(Arr::get($response, 'refresh_token')) ->setExpiresIn(Arr::get($response, 'expires_in')); } This is in the vendor/laravel/socialite/src/Two/AbstractProvider.php So for example my real error was:

March 4, 2018 Read
Wrapping Libraries in Services JS

Just a note to self that when using libraries like sweetalert for example and then I want to convert to sweetalert2, it would have saved a lot of time to wrap it into a “service” and import that. For example I made this js file services/Alerts.js: import swal from 'sweetalert2'; export default { send(title, message, error = false) { swal( { type: error ? "error" : "success", title: title, text: message } ); } } Then import it into the app or into the component that needs it.

March 1, 2018 Read
Passing from Blade to VueJs

A lot of posts had this style. I ended up just needing this: The controller simply does this:

February 24, 2018 Read
Docker Laravel and Cron

This to this post here for the idea. Basically running cron in Docker is easy BUT once the Host had more than one Docker client cron stopped working. No clue why but to solve this I did two things One made a script that was on the Docker Client /scheduler.sh #!/bin/bash php /app/artisan schedule:run --verbose --no-interaction >> /dev/null 2>&1 sleep 60 Then I did this in the Dockerfile COPY scheduler.sh / RUN chmod 755 /scheduler.

February 16, 2018 Read
Laravel and AWS Rekognition

….

February 16, 2018 Read
Pusher and Laravel Updates

Getting error “Did you forget to specify the cluster when creating the Pusher instance” Then need to set config/broadcasting.php: 'pusher' => [ 'driver' => 'pusher', 'key' => env('PUSHER_KEY'), 'secret' => env('PUSHER_SECRET'), 'app_id' => env('PUSHER_APP_ID'), 'options' => [ // ], ], to 'pusher' => [ 'driver' => 'pusher', 'key' => env('PUSHER_KEY'), 'secret' => env('PUSHER_SECRET'), 'app_id' => env('PUSHER_APP_ID'), 'options' => [ "cluster" => 'us2', "encrypted" => true ], ], And if still calling pusher manually in your js update to be:

February 14, 2018 Read
Dusk and Production (with Dusk disabled)

In DatabaseServiceProvider.php line 78: Class 'Faker\Factory' not found I had a ton if issues getting dusk on production, especially since production would run composer install --no-dev --prefer-dist --no-interaction To get around this issue I had to do a few things One, if you are stuck and can not even run php artisan on the server: rm bootstrap/cache/services.php rm bootstrap/cache/packages.php Two, turn off auto discovery for Dusk and just add it to the app/Providers/AppServiceProvider.

February 5, 2018 Read