Make ClassicPress a 12 Factor App...ish

WordPress has long followed an operational model that makes deploying, updating, and maintaining it automatically difficult.

While the formal Twelve-Factor App structure adheres a little too rigidly to the Heroku deployment model, it offers a number of advancements that would greatly aid operational concerns with ClassicPress.

For reference, I’m referring to this:

As an example, implementation of configuration in the environment - not on the filesystem - would improve flexibility and make operating ClassicPress in a Docker container more viable. An excellent library for this exists in the form of Vance Lucas’s phpdotenv: GitHub - vlucas/phpdotenv: Loads environment variables from `.env` to `getenv()`, `$_ENV` and `$_SERVER` automagically.

Another part of the Twelve-Factor App model that would help in operations is logging. WordPress’s logging model is just to rely on the reverse proxy serving it. ClassicPress would benefit from adopting Jordi Boggiano’s monolog library (GitHub - Seldaek/monolog: Sends your logs to files, sockets, inboxes, databases and various web services), as it implements the PSR-3 standard and makes logging much more manageable from an operations standpoint.

Note: this petition has huge scope, and would be best served by being adopted as an overarching strategy, rather than an atomic change.

Read-only archive:

Author: Ben Overmyer

Vote count: 8

Status: open


This topic was automatically closed after 3 days. New replies are no longer allowed.