You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.
User should be able to specify schedules in their local timezone (as this is easiest/most natural) rather than the timezone of the server running tuner, in cases where the two are not the same.
Practically, there are probably two cases for timezone placement:
Host is running in the user's local time (i.e. no difference)
Host is running in UTC
but it might as well be solved in a general way. I fall into the latter (my homelab server runs in UTC) so I will probably implement this, but it's not a P0 because it's mostly just an annoyance to have to specify the crons in UTC.
This can be implemented as a pre-processing of the cron expressions, or if I ever build a front-end then it's probably in scope for that to just do conversion of date-time-picker output before constructing a cron expression (which would be about infinitely more turnkey).
The text was updated successfully, but these errors were encountered:
User should be able to specify schedules in their local timezone (as this is easiest/most natural) rather than the timezone of the server running tuner, in cases where the two are not the same.
Practically, there are probably two cases for timezone placement:
but it might as well be solved in a general way. I fall into the latter (my homelab server runs in UTC) so I will probably implement this, but it's not a P0 because it's mostly just an annoyance to have to specify the crons in UTC.
This can be implemented as a pre-processing of the cron expressions, or if I ever build a front-end then it's probably in scope for that to just do conversion of date-time-picker output before constructing a cron expression (which would be about infinitely more turnkey).
The text was updated successfully, but these errors were encountered: