DevOps

A Drupal job title can conceal a much wider engineering remit in government work. The platform stays central, but the surrounding responsibilities span much more of the application lifecycle. ...more

Several changes in Lumen can disrupt an otherwise routine upgrade if project-owned state is left untouched. Admin modules, lock files, CI settings, and custom linting rules sit outside what the installer can safely change. ...more

A known database state can now return automatically when a DDEV project starts with an empty database, removing a repeated restoration step from local Drupal work. ...more

For Drupal teams responsible for production systems, the session offers a look at how a former Acquia senior product manager is approaching observability across multiple DevOps tools. ...more

A complete-looking documentation run later proved unreliable when Omega8 subjected the output to deeper verification against BOA's code. That failure changed what the team demanded from its later agent workflows. ...more

Data can remain in one jurisdiction while account ownership, administrator access, software dependencies, and exit control sit elsewhere. ...more

Drupal site security rarely stops at core and module updates. Canonical’s survey shows why package provenance, Linux maintenance, and patch ownership remain part of delivery risk. ...more

Drupal hosting choices are increasingly tied to who controls the cloud account, not only who manages the site. DevPanel’s post uses that question to frame vendor lock-in as an infrastructure and procurement concern. ...more

Pantheon has outlined several product updates in its second-quarter announcement. The changes include Next.js support, direct GitHub integration, Solr 9 beta availability, and Customer Scheduled Jobs. The update is relevant to Drupal teams using Pantheon for search, deployment workflows, decoupled builds, and recurring site automation. ...more

A recent Drupal security advisory prompted familiar public focus on patch deployment speed, but Dan Frost of Adaptive argues that preparation is a stronger measure of security maturity. His article examines how inventory management, deployment planning, testing, rollback procedures, mitigation coverage, and communication workflows shape effective responses to critical vulnerabilities. The analysis frames incident response as an operational discipline rather than a race to publish the fastest patching claim. ...more

John Locke of Freelock describes Argo, a parent-directory workflow for managing AI-assisted development across related repositories. The approach uses shared instruction files, repository-specific guidance, and context markers to help coding agents operate with clearer project boundaries while keeping implementation work focused within individual codebases. ...more

A recent analysis by Dan Frost argues that effective security response depends on preparation rather than patching speed alone. The article examines how testing workflows, deployment governance, rollback planning, and infrastructure awareness help organisations manage security updates without introducing new operational risks. It positions patch management as one component of a broader resilience strategy focused on stability, risk assessment, and recovery readiness. ...more