atualizacoes-execucao.php library

Path in the Gestor bibliotecas/atualizacoes-execucao.php

Basis of POST /_api/system/update with action=run and run-status (req-201 / BATCH-209). It is pure (no Gestor). What runs on the server is the same CLI updater (atualizacoes-sistema.php), with lock, snapshot, dump, check and automatic restore.

Usage

• atualizacoes_execucao_argv($opcoes, $dominio) translates API options into updater arguments. It accepts only those in ATUALIZACOES_EXECUCAO_OPCOES and sanitizes values (tag, URL without &/;/quotes, IP, tables, days). What fails comes back in recusadas. It always adds --log-stdout, so the run log carries the snapshot and check lines.

• atualizacoes_execucao_php_cli($preferido) finds the command-line PHP. Inside PHP-FPM, PHP_BINARY is FPM itself.

• atualizacoes_execucao_disparar($base, $id, $argv, $meta, $php) triggers in the background (nohup and setsid), with output in <id>.log and the exit code in <id>.exit, inside temp/atualizacoes/runs/. It uses pipes, not /dev/null, because HestiaCP's open_basedir blocks opening /dev/null from PHP. On failure it writes exit code 1 so the run is not left "running".

• atualizacoes_execucao_estado($log, $exit) reads the state: no code yet means running; updater codes become success, rolled_back (6), locked (8) and error-*. It also extracts snapshot, check, automatic restore, errors and the end of the log.

• atualizacoes_execucao_novo_id(), atualizacoes_execucao_id_valido() and atualizacoes_execucao_pasta() handle the run-<date>-<suffix> id and the folder.

Functions

atualizacoes_execucao_id_valido(string $id): bool

atualizacoes_execucao_novo_id(): string

atualizacoes_execucao_pasta(string $base): string

atualizacoes_execucao_argv(array $opcoes, string $dominio): array

atualizacoes_execucao_php_cli(?string $preferido = null): string

atualizacoes_execucao_disparar(string $base, string $id, array $argv, array $meta, string $php): array

atualizacoes_execucao_estado(string $log, ?string $exit): array