Unable to set default timezone for new user

[szpak]

I've set up Miniflux 2.0.35 with Podman (an alternative to Docker) and it works nicely. It initialized with UTC as a time zone and I wanted to change it. I set a time zone for a container to "Europe/Warsaw" (and recreated it), set the TZ environment variable (and recreated it), but for a new user the time zone is always set to UTC.

I saw that a time zone is set for an user in a database and I can change it after creation, but I wonder, if Miniflux takes a system time zone into account when it starts up (or rather the global value is persistent in a database after the initial execution and should be changed there)?

[fguillot]

I saw that a time zone is set for an user in a database and I can change it after creation, but I wonder, if Miniflux takes a system time zone into account when it starts up (or rather the global value is persistent in a database after the initial execution and should be changed there)?

Miniflux uses the default value specified in the schema.

miniflux2=# \d users
                                            Table "public.users"
       Column       |           Type           | Collation | Nullable |               Default
--------------------+--------------------------+-----------+----------+-------------------------------------
 id                 | integer                  |           | not null | nextval('users_id_seq'::regclass)
 username           | text                     |           | not null |
 password           | text                     |           |          |
 is_admin           | boolean                  |           |          | false
 language           | text                     |           |          | 'en_US'::text
 timezone           | text                     |           |          | 'UTC'::text
....

[szpak]

Thanks @fguillot . It shows how to change it in my case.

As I see UTC is hardcoded in the initial migration:

v2/database/migrations.go

Line 27 in 4b6e46d

timezone text default 'UTC',

I wonder, if you think it might make sense to take that value from the system time zone during the initial migration or maybe - to prevent confusion - to have a dedicated (optional) environment to achieve that?