When building a website for a client that wants to be able to manage content, Laravel's language files aren't ideal since you can't edit them without diving into a bundle of text files. We recently decided to drop all the lang files in our custom CMS in favor of persisting translations in the database, which allows us to build a custom interface for managing them. This post is a quick overview on overwriting Laravel's default translation loader, which means you can keep using the lang method while fetching the translations from a database. Writing a custom loader is easier than it sounds. First we'll set up our translation models, then we'll write our loader, and finally register it in our application.
Uptime and SSL certificate monitoring doesn't have to be boring, confusing or expensive. Together with my buddy Mattias Geniar I'm currently building Oh Dear: a webapp to keep an eye on the health of your websites. Register here to try it out. (sponsored link)