Skip to content

Conversation

fpicosm
Copy link

@fpicosm fpicosm commented Apr 8, 2025

No description provided.

@taylorotwell
Copy link
Member

Should just be UTC by default.

@fpicosm
Copy link
Author

fpicosm commented Apr 8, 2025

@taylorotwell Why? I mean, all variables in config/app have their related env variable.

By default the timezone should be UTC, ok, this is covered with 'timezone' => env('APP_TIMEZONE', 'UTC'), but what if I want to use "Europe/Madrid" for example? I need to edit the config file instead of the env file, like we do with the rest of variables

@GrahamCampbell
Copy link
Member

It's generally not good practice to run the backend on anything other than UTC, regardless of the location of your business or customers. If you'd really like to change this, against recommendations, it's still possible to do by making this change directly in your own config file.

@fpicosm
Copy link
Author

fpicosm commented Apr 9, 2025

It's generally not good practice to run the backend on anything other than UTC, regardless of the location of your business or customers. If you'd really like to change this, against recommendations, it's still possible to do by making this change directly in your own config file.

I understand. But in that case, I don't get the point to have a "timestampsTz" option creating migrations, for example 😂

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.

3 participants