As I was designing an API this last week, I decided that I wanted to obfuscate object ids in the JSON messages I sent back and forth. To do so, I wanted to use the terrific Hashids library, so I sniffed out this Laravel wrapper for it.
composer.json "require": { … "hashids/hashids": "1.0.6", "vinkla/hashids": "2.2.2", … } Note: You should peg your versions in Composer so you avoid incompatible hashes down the road, especially if you store computed hashes for use or comparison later.
I was fiddling with the blog over the last few days, updating the look-and-feel a little bit, as well as doing some housekeeping on the back end. One thing I wanted to do was migrate my posts from an old model PostModel to just plain Post. (I know, what a horrible name I started with. I have learned!)
This was no big deal, as I pretty much just had to do a quick find-and-replace for App\PostModel in my code.
Yesterday, I created a GitHub organization so that I could house all of the projects my LLC is working on under one roof. The re-homing process from my individual GitHub user account to the organization could not have been smoother.
Once the repositories were in place, I went to spin up a new Forge instance for a new site I was working on. When I tried to deploy from GitHub, I got this error:
If you read my last In Brief post, you may have tried setting up a cron job to run mysqldump nightly, gone back to check the results the following day and found a zero byte file where you expected to see a dumpfile.
-rw-rw-r– 1 forge forge 0 Mar 5 00:00 dump-nightly.sql Don’t worry! The backup still ran, but Forge does some auto-magic output redirection that had me guessing for a little while.
(Update: Can’t believe I forgot Laracasts when I wrote about the Laravel ecosystem below.)
First, a confession. I’ve only been doing “serious” Laravel development for about four or five weeks now.
In fact, it has been about a decade since I did any serious PHP development at all.
I’m still getting my hands dirty digging through how Laravel works, and I’m certainly a way off from “mastery” of the framework, but the single best way to learn a new language, technology or framework is to have a project, a timeline, and to just get cracking.
