ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine whether Drupal core's automatic database log pruning can remove messages from a failed deployment before an administrator reviews the Recent log entries report. Constraints and uncertainty The dblog module retains a configurable maximum number of entries and deletes older entries during cron. The default limit, administration path, and pruning
A step‑by‑step diagnostic guide for Moodle cron and scheduled task failures: recognize stuck runs, map symptoms to root causes, run ordered checks, apply targeted fixes, and know when to escalate.
Keep Moodle background work on a single CLI cron entrypoint run as the web service user, with observable task logs and clear trust and data boundaries. Know when to move to a queue or worker split.
Decide whether to use WordPress’s built‑in WP‑Cron or a system‑level cron job. Compare reliability, performance, and hosting constraints, and see a step‑by‑step example of disabling WP‑Cron and setting up a deterministic cron entry.
How to design background job processing in Drupal using the Queue API: minimal worker setup, trust boundaries, operational checks, and when to move to an external broker.
A decision guide for Moodle administrators comparing CLI cron, web cron, and systemd-managed timers across security, reliability, and hosting constraints.
A diagnostic guide for Magento 2 indexers stuck in 'working' state or missing scheduled reindexes, covering cron, database locks, search engine health, and safe recovery.
A decision guide comparing cron, systemd timers, and at/batch for scheduled tasks on Unix‑like systems, with a concrete systemd timer example and verification steps.
Learn how to create a Moodle scheduled task that runs periodic PHP code, with a concrete example for cleaning up old log entries, testing via CLI, and verification steps.
drupal
magento
unix
php