[GH-ISSUE #32] Timezone and x-axis of uptime monitor #19

Closed
opened 2026-02-27 09:12:37 +03:00 by kerem · 4 comments
Owner

Originally created by @martin-ro on GitHub (Sep 4, 2020).
Original GitHub issue: https://github.com/maelstrom-cms/odin/issues/32

Hi,

I think the timezone shouldn't be hard-coded in app/Console/Kernel.php but using the config from config/app.pp.

protected function scheduleTimezone()
    {
        return 'Europe/London';
    }

--->

protected function scheduleTimezone()
    {
        return config('app.timezone');
    }

so we can set the timezone in .env.

Would you accept a PR?

Another thing I noticed is that the timescale for the uptime monitor goes from right-to-left. Is this intentional? Normally timescales go ltr.

Originally created by @martin-ro on GitHub (Sep 4, 2020). Original GitHub issue: https://github.com/maelstrom-cms/odin/issues/32 Hi, I think the timezone shouldn't be hard-coded in `app/Console/Kernel.php` but using the config from `config/app.pp`. ``` protected function scheduleTimezone() { return 'Europe/London'; } ``` ---> ``` protected function scheduleTimezone() { return config('app.timezone'); } ``` so we can set the timezone in `.env`. Would you accept a PR? Another thing I noticed is that the timescale for the uptime monitor goes from right-to-left. Is this intentional? Normally timescales go ltr.
kerem 2026-02-27 09:12:37 +03:00
Author
Owner

@OwenMelbz commented on GitHub (Sep 13, 2020):

Hi,

Yeah we'd accept a PR to configure the time zone from the env as long as it defaults to London :)

I'm not sure what you mean about the right to left thing sorry?

Thanks

<!-- gh-comment-id:691672199 --> @OwenMelbz commented on GitHub (Sep 13, 2020): Hi, Yeah we'd accept a PR to configure the time zone from the env as long as it defaults to London :) I'm not sure what you mean about the right to left thing sorry? Thanks
Author
Owner

@dsturm commented on GitHub (Oct 20, 2020):

Hey @OwenMelbz,

about the "right-to-left" thing: I think what @martin-ro means is that normally a time scale would draw from oldest (left) to newest (right) entries. Currently it is the other way around for the Response Time chart having the latest data on the left.

<!-- gh-comment-id:712666756 --> @dsturm commented on GitHub (Oct 20, 2020): Hey @OwenMelbz, about the "right-to-left" thing: I think what @martin-ro means is that *normally* a time scale would draw from oldest (left) to newest (right) entries. Currently it is the other way around for the Response Time chart having the latest data on the left.
Author
Owner

@dsturm commented on GitHub (Oct 20, 2020):

... and towards the time zone configuration:

I think, since the core class already uses the config key app.schedule_timezone and app.timezone as fallback, it should be safe to remove the method scheduleTimezone from app/Console/Kernel.php.

<!-- gh-comment-id:712688058 --> @dsturm commented on GitHub (Oct 20, 2020): ... and towards the time zone configuration: I think, since the [core class already uses the config key `app.schedule_timezone` and `app.timezone` as fallback](https://github.com/laravel/framework/blob/2cd2877fb003d395b5b292a363b917e31cf60200/src/Illuminate/Foundation/Console/Kernel.php#L171), it should be safe to remove the method `scheduleTimezone` from `app/Console/Kernel.php`.
Author
Owner

@OwenMelbz commented on GitHub (Oct 20, 2020):

Thanks for the help 👍

Have merged and closed :)

<!-- gh-comment-id:712777743 --> @OwenMelbz commented on GitHub (Oct 20, 2020): Thanks for the help 👍 Have merged and closed :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/odin-maelstrom-cms#19
No description provided.