Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
With Slim 4, we have continued the tradition of allowing you to use the framework in the way that best fits you and your project. You can create a Slim application entirely in a single file, suitable for prototyping through to a few files for a simple web hook or serverless action, all the way to a fully-decoupled application suitable for an enterprise.
From my point of view, the big changes with Slim 4 are:
I recently set up a new WordPress-based website and local Docker-based development environment. This post documents what I did so that I can do it again next time! As I'm not in the WordPress world, many things are strange to me and I'm indebted to Jenny Wong for pointing me in the right direction on numerous occasions and being very patient with my questions! Thanks Jenny!
There's always ancillary files and directories in a project that aren't part of the actual website, so I have put the WordPress site in a subdirectory called app and then I have room for other stuff. My project's root directory looks like this:
I have a handy bash script that transcodes videos using Don Meton’s video_transcoding tools. This script was written in a hurry, and one limitation it had was that it re-transcoded any source file even if the output file already existed.
The script looked like this: