Normally, with Laravel (@laravelphp on Twitter), if you create a model and use the “-m” or “–migration” flag to create the accompanying migration, it will pluralize the table.
So for example “User” model will use a “users” table; “Vehicle” model will use a “vehicles” table.
I just discovered however, that if you create a “Data” model, the table will also be created as “data” – not “datas”. It makes complete sense as datas isn’t a word.
I love using this framework.
Jams were a type of content popularized by the website This is my jam.
This is my jam has since gone into read-only archive mode. This is such a great way of closing a website — especially one whose content is mostly community-created.
I started to use the site at the end of last year to start saving songs that stood out to me at a particular time.
Thanks to This is my jam for making me an archive of my own. This means I haven’t lost all of my data with them just because they have closed doors.
I still love the idea of saving individual “jams” though, so I have implemented it on my own site as of today. I have also pulled my old jams into my site. Going forwards I look forward to documenting any new and/or forgotten gems that I hear in the future. They will all be found on my Jams page.
Arrived at Tinseltown. May have to partake in a giant milkshake.
Watching American Horror Story series 4 episode 11: Magical Thinking.
Thank you Google for breaking the images on google play music. src=”” indeed.
I’ve been using Laravel for my personal website for about eight months now and haven’t looked back since.
This huge advantage to my rebuilding it in that way — from its original WordPress foundations — was that I had a crash course in using Laravel as well as learning some best practices as well.
Now that I have been using my site daily for all this time, I have found places where it has got messy — unavoidable through the learning experience — as well as places where I want to refine how I publish.
At the moment I am using what are called explicit post types. Meaning that I manually choose which post type a particular post belongs to before publishing — picking the appropriate create form to publish from.
However I have been thinking more and more about implicit post types — post types whose contents define what sort of post it is. Going the way of implicit may also see me abolishing the need for post-type-specific areas of my site.
I could still do this to some degree I suppose. e.g. If a post doesn’t have a title, it’s a note; If it has a location, it’s a checkin; etc.
The only way to see how this is going to go is to build it and actually publish with it for a while, I guess.
Update 8th February 2021: I now use WordPress for my website and have done for a few years now.
Explore
If you want to search, or just get an overview of my stuff, the explore page is a good place to start.
Any interesting websites and/or people I have found online, I link them on my blogroll page.
I keep a record of things i use on my… well… my “uses” page.
Blog Categories
Archive
