Cron Jobs Improvements for FlyEnv

[ibraimfarag]

Cron Jobs Improvements for FlyEnv

Overview

This update improves the Cron Jobs experience inside FlyEnv, especially for local development and testing on Windows.

Why This Update Matters

As a Laravel/PHP developer, I need to test Cron Jobs locally on Windows before deploying to production.

I also rely on scheduled automation tasks that should run at specific times, and I need to verify behavior early (success/failure, command output, and timing) before pushing code.

What Was Added

1) Cron Jobs Core Behavior

• Fixed storage initialization issue for first-time usage (ENOENT on cron-jobs.json).
• Added automatic creation of the .flyenv storage directory before writing Cron data.
• Improved Work Directory handling in Add/Edit dialog:
  • Defaults to website root.
  • Still editable.
  • Reset and save behavior keeps a safe fallback.

2) Scheduler and Runtime Metadata

• Added internal scheduler logic in the Cron module.
• Added automatic run metadata updates:
  • lastRunTime
  • nextRunTime
  • lastOutput
  • lastError
  • lastExitCode
• Added immediate run support for manual testing with persisted results.

3) UI/UX Enhancements

• Simplified Cron header and top close button layout.
• Improved translation fallback handling for stat labels.
• Added real-time list refresh polling so run times update without manual refresh.
• Added visual status icons:
  • Success icon when the last run exits with code 0.
  • Failed icon when the last run exits with non-zero code.
  • Paused icon for disabled or not-yet-run jobs.
• Replaced action text labels with action icons (run, edit, delete).
• Added dedicated action icon to open full execution output.

4) Output Visibility

• Added output viewing dialog from Actions.
• Shows complete run details:
  • Job name
  • Command
  • Exit code
  • Duration
  • Last run timestamp
  • Full STDOUT
  • Full STDERR

Developer Workflow (Laravel/PHP on Windows)

This update supports the following local workflow:

1. Create and edit Cron Jobs for Laravel/PHP commands.
2. Test schedules and commands locally on Windows.
3. Validate timing and execution status before deployment.
4. Inspect full output/errors directly from the app.
5. Deploy with higher confidence after local verification.

Notes

• This is focused on local development/testing reliability.
• The goal is to catch schedule/output issues early and reduce production surprises.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.