Skip to content
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.

Support timezone conversion for source schedules #3

Open
overholts opened this issue Nov 16, 2019 · 0 comments
Open

Support timezone conversion for source schedules #3

overholts opened this issue Nov 16, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@overholts
Copy link
Owner

overholts commented Nov 16, 2019

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:

  1. Host is running in the user's local time (i.e. no difference)
  2. 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).

@overholts overholts added the enhancement New feature or request label Nov 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant