Defensive : timeout shell sur pagedjs-cli + message d'erreur explicite
All checks were successful
Deploy / deploy (push) Successful in 18s
All checks were successful
Deploy / deploy (push) Successful in 18s
Wrapper `timeout 360` autour de pagedjs-cli pour SIGTERM-er le process si Chrome hang au-delà du protocolTimeout interne. Détecte le code 124 du shell timeout pour donner un message clair à l'utilisateur. Cron de cleanup orphan installé manuellement sur le VPS dans /etc/cron.d/web2print-cleanup (toutes les 15 min, appelle worker.php --cleanup). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
56f5a45b7d
commit
8c8c0b0b91
2 changed files with 13 additions and 1 deletions
|
|
@ -20,6 +20,7 @@ return [
|
|||
|
||||
// Jobs asynchrones
|
||||
'job_max_age' => 3600, // 1h, age au-delà duquel un job orphelin est supprimé
|
||||
'job_max_duration' => 360, // 6 min, kill SIGTERM via `timeout` si pagedjs-cli ne termine pas
|
||||
|
||||
// Limites
|
||||
'max_html_size' => 5 * 1024 * 1024, // 5 MB
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue