CoreCluster · Ship

PHP, MariaDB and crons

Choose PHP 7.4 to 8.5, upgrade MariaDB, set PHP limits and schedule crons, site by site, from the panel.

Start free for 30 days ← Back to CoreCluster
manage.corefinity.com/managed-clusters
Runtime kilnandcopse.com · Magento 2

Version and PHP setting changes restart the site, about a minute. Crons apply live.

Restart PHP Save settings

Versions

PHP
8.28.38.48.5
MariaDB
11.4 upgrade to 11.8 available
Object cache
Redis On
Search
OpenSearch 2 Healthy

PHP settings

  • memory_limit1024M
  • upload_max_filesize64M
  • max_execution_time300
Crons 2 jobs · run as web
Crons on
bin/magento cron:run Every minute Ran 10:41 Edit
bin/magento indexer:reindex Nightly at 02:00 Ran 02:00 Edit
{  How it works  }

PHP, MariaDB and crons, step by step

  1. 1

    Choose the PHP version

    Switch between the versions the platform supports. The site restarts once, in about a minute.

    manage.corefinity.com/managed-clusters
    The Change PHP version dialog, listing PHP 8.2, 8.3, 8.4 and 8.5
  2. 2

    Upgrade MariaDB a step at a time

    Move up one release at a time. A database cannot go back, so the system tables are backed up first.

    manage.corefinity.com/managed-clusters
    The PHP and MariaDB cards on the Runtime tab, with Change version and Upgrade
  3. 3

    Set PHP limits

    Raise the memory limit, upload size or execution time, within what the site’s size allows. Saving restarts the site.

    manage.corefinity.com/managed-clusters
    The PHP settings card: memory limit, upload size and max execution time, each with its limits
  4. 4

    Add a scheduled task

    Name it, pick a schedule and type the command. The panel shows the next runs before you save.

    manage.corefinity.com/managed-clusters
    Add a task marrowtide.co.uk · production
    Task name Regenerate thumbnails
    Schedule Every minuteEvery 5 minutesHourlyDailyWeeklyMonthlyCustom
    at02:30 30 2 * * * Runs next 7, 8 and 9 Oct at 02:30, London time
    Command wp media regenerate --only-missing --yes
    Time limit 15 minutes1 hour6 hours Skip a run while the last one is still going
    Runs as web in htdocs. Applies within a minute or two. Cancel Add task
  5. 5

    Save, then watch each run

    Cron changes apply in a minute or two, with no restart. Each task shows its last result and next run.

    manage.corefinity.com/managed-clusters
    Crons marrowtide.co.uk · production

    Scheduled tasks run as web in htdocs. Changes apply within a minute or two.

    Scheduled tasks: On Add task
    OnTaskScheduleLast run
    WordPress cronBuilt in · wp cron event run --due-now Every 5 minutes*/5 * * * * Succeeded 12:10 · 2 sNext 12:15
    Sync the product feedphp tools/sync-feed.php Every 15 minutes*/15 * * * * Skipped 12:00Previous run still going ⋯
    Regenerate thumbnails Newwp media regenerate --only-missing --yes Daily at 02:3030 2 * * * Never runNext 7 Oct 02:30 ⋯
    1 unsaved change Times are London time. Discard Save changes
manage.corefinity.com/managed-clusters
The Change PHP version dialog, listing PHP 8.2, 8.3, 8.4 and 8.5
manage.corefinity.com/managed-clusters
The PHP and MariaDB cards on the Runtime tab, with Change version and Upgrade
manage.corefinity.com/managed-clusters
The PHP settings card: memory limit, upload size and max execution time, each with its limits
manage.corefinity.com/managed-clusters
Add a task marrowtide.co.uk · production
Task name Regenerate thumbnails
Schedule Every minuteEvery 5 minutesHourlyDailyWeeklyMonthlyCustom
at02:30 30 2 * * * Runs next 7, 8 and 9 Oct at 02:30, London time
Command wp media regenerate --only-missing --yes
Time limit 15 minutes1 hour6 hours Skip a run while the last one is still going
Runs as web in htdocs. Applies within a minute or two. Cancel Add task
manage.corefinity.com/managed-clusters
Crons marrowtide.co.uk · production

Scheduled tasks run as web in htdocs. Changes apply within a minute or two.

Scheduled tasks: On Add task
OnTaskScheduleLast run
WordPress cronBuilt in · wp cron event run --due-now Every 5 minutes*/5 * * * * Succeeded 12:10 · 2 sNext 12:15
Sync the product feedphp tools/sync-feed.php Every 15 minutes*/15 * * * * Skipped 12:00Previous run still going ⋯
Regenerate thumbnails Newwp media regenerate --only-missing --yes Daily at 02:3030 2 * * * Never runNext 7 Oct 02:30 ⋯
1 unsaved change Times are London time. Discard Save changes
{  What you can set  }

Options and limits

Everything here is per site or per environment, from the panel, with every change in the activity log.

PHP
WordPress 8.2 to 8.5, Laravel 8.3 to 8.5, Magento 2 8.3 and 8.4. New sites start on 8.3.
MariaDB
11.4, 11.8 and 12.3; Magento 2 on 11.4 and 11.8. Upgrades only, one release at a time.
Memory limit
From 128 MB up to the PHP container’s memory less 256 MB, in 64 MB steps. A bigger site size raises it.
Upload size
2 MB to 1 GB. The post size follows it.
Max execution time
60, 120 or 300 seconds. Longer work belongs in a cron or the terminal.
Crons
Up to 49 tasks of your own per site, in London time. A time limit of 15 minutes, 1 hour or 6 hours.
Built-in cron
WordPress cron every 5 minutes; Laravel’s scheduler and Magento’s cron every minute. It can be switched off, not edited.
Restarts
A version or PHP setting change restarts the site once. Cron changes need no restart.

Questions about php, mariadb and crons

Yes. PHP is set per site, and each environment has its own. Staging can try PHP 8.4 while production stays on 8.3.

No. MariaDB cannot move a database back to an older version, so the panel only upgrades, one release at a time. The system tables are backed up first, and the site is snapshotted daily.

Scheduled tasks start off on staging and development environments, and on a site with no domain yet. Turn them on with one switch when you need them.

← PreviousSSH, SFTP and terminal Next →Snapshots
Every walkthrough Back to CoreCluster →
Build
Launch
Ship
Protect
{  CoreCluster  }

See php, mariadb and crons on your own cluster

Tell us how many sites you run and on what. An engineer sizes a cluster with you and shows you the panel on a live one.

By sending this message you agree to our Privacy Policy .