Limits of Ghost’s Scheduled Post Time‑Zone Interpretation

Goal

Determine how Ghost’s scheduler maps a user‑entered publish time to the UTC timestamp stored in the database when the site’s timezone setting is configured.

Current Constraints

Ghost records all timestamps in UTC, and the timezone key only affects front‑end formatting via moment‑timezone. The scheduler, executed by a background worker, treats the time entered in the admin UI as UTC regardless of the configured zone, potentially causing a mismatch for authors in other regions.

Unresolved Decision

It is unclear whether Ghost offers a configuration or API to make the scheduler honor the timezone value, or if the only solution is to adjust the input time manually.

Questions

1. When a post is scheduled from the admin panel, does Ghost interpret the entered time as UTC or as the configured timezone?
2. What UTC value is stored in the published_at column when a user schedules for 9:00 AM in a non‑UTC zone?
3. Is there a documented way to change the scheduler’s interpretation to match the configured time zone?