mirror of
https://github.com/maelstrom-cms/odin.git
synced 2026-04-25 08:16:03 +03:00
[GH-ISSUE #32] Timezone and x-axis of uptime monitor #19
Labels
No labels
bug
enhancement
help wanted
pull-request
question
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/odin-maelstrom-cms#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.phpbut using the config fromconfig/app.pp.--->
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.
@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
@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.
@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_timezoneandapp.timezoneas fallback, it should be safe to remove the methodscheduleTimezonefromapp/Console/Kernel.php.@OwenMelbz commented on GitHub (Oct 20, 2020):
Thanks for the help 👍
Have merged and closed :)