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.
Secure shell into file server. Install samba if not already present: Create samba password with : sudo smbpasswd -a YOUR_USERNAME Configuring the share: Restart samba:
A handy way to have some of your routes skip the middleware for CSRF protection. Handy in some situations.
The Issue I wanted to build a site with some custom post types, taxonomies and the like. But what if somebody who has used my theme decided to try another theme later on? What guarantee do they have that those custom post types will be recognized by a future theme? None — that’s what. WordPress obviously has its plugin directory, which is designed for adding in pieces of functionality that should span across themes. But what if these are essential…