Skip to content

Conversation

@RJV333
Copy link
Contributor

@RJV333 RJV333 commented Feb 2, 2026

What is the goal of this PR and why is this important?

#819 Sets Pacific Time as the default time zone for the app.

In a followup PR, we can add a configuration to the User for a customizable timezone that, if used, can then be used to supercede this default Time.zone

My understanding is that updating config.time_zone won't change how datetimes are stored, since Rails always stores datetimes in the database in UTC. When users submit a datetime, Rails will think of it as originating in Pacific Time, and then convert it to UTC for storage, and then when it's pulled for display convert from UTC to Pacific again.

Open to any alternative ideas though.

@jmilljr24
Copy link
Collaborator

Timezones make my head spin. I believe you are correct that config.time_zone only affects rails time not the DB time. However thoughtbot recommends against changing this.

The default time zone in Rails is UTC. As tempting as it may seem, it is best to leave the application-wide time zone as UTC and instead allow each individual user to set their own time zone.

I'm not sure if there would be any consequences of setting time_zone now and adding a user setting later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants