Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam scelerisque ut mi vitae cursus. Morbi ullamcorper odio ut molestie pellentesque. In sit amet neque accumsan, porttitor lectus in, elementum sem. Proin vehicula magna eu diam volutpat, id semper enim feugiat. Aliquam fermentum libero tortor, vitae venenatis ligula elementum id. Vestibulum a maximus diam.
Fusce lorem quam, scelerisque non turpis vel, sollicitudin efficitur dolor. Nunc quis efficitur sapien. Curabitur venenatis tortor augue, a consequat arcu rhoncus a. Curabitur velit diam, iaculis quis varius ut, varius at augue. Fusce mollis et ante ac egestas. Pellentesque felis metus, lobortis non purus pharetra, hendrerit ornare nulla. Etiam a neque tellus. Etiam risus dui, imperdiet vel odio eu, posuere auctor quam. Maecenas vulputate semper risus, non semper felis pellentesque et.
Nearly every application in existence requires some form of configuration. After
all, no two instances of the same app are exactly the same. The "tried and true"
(read "quick and dirty") way of doing this has conventionally been with arrays.
This works well for most basic configuration values of scalar types, however,
sometimes it may be necessary to configure complex objects.
As a PHP developer I often find myself having to run executable files installed to a project via Composer (e.g. php-cs-fixer, phpunit, psysh, etc.). These binary files typically reside in vendor/bin relative to the root of a project and in order to run these binary files from the project root I would need to cd into the vendor/bin directory first or type out the relative path (e.g. vendor/bin/php-cs-fixer fix) every time I wanted to run one of these executables.
Use a Linux system long enough and eventually you'll need to schedule a
recurring task. Of course the defacto scheduler is cron (and there's nothing
inherently wrong with it) but I've grown to like the flexibility and features of
systemd timers. Some of the benefits they provide over cron include:
