starred/pocket-id
1
0
Fork 0
mirror of https://github.com/pocket-id/pocket-id.git synced 2026-07-16 05:54:01 +03:00
Code Issues 61 Packages Projects Releases 21 Wiki Activity

🐛 Bug Report: changing some env config variables seems to have no effect #271

New Issue
Closed
opened 2026-02-04 18:31:04 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 18:31:04 +03:00
Owner
Copy Link

Originally created by @andreas-soroko on GitHub (May 5, 2025).

Reproduction steps

  • have existing pocket-id instance ( had 0.48.0 before )
  • update to 0.51.1
  • re-deployed pocket-id
  • changing EMAIL_ONE_TIME_ACCESS_ENABLED to true
  • restart pocket id
  • option is still disabled

Expected behavior

Changing the env values updates correctly the config in pocket-id

Actual Behavior

i updated an existing pocket-id instance and after the update i wanted to set the value EMAIL_ONE_TIME_ACCESS_ENABLED to true.
After a restart, the option in the UI was still disabled. Then i thought, okay - maybe the key doesn't work and set it myself via the ui and set PUBLIC_UI_CONFIG_DISABLED back to false - restart, again nothing happened.
I then changed the SMTP_HOST value as a test - worked, but the other values were not updated.

Is there a problem?

you can also set Email Login Code from Admin in the ui, but there doesn't seem to be an env key for this, or is this also controlled via EMAIL_ONE_TIME_ACCESS_ENABLED?

Version and Environment

version: 0.51.1

Log Output

No response

Originally created by @andreas-soroko on GitHub (May 5, 2025). ### Reproduction steps - have existing pocket-id instance ( had 0.48.0 before ) - update to 0.51.1 - re-deployed pocket-id - changing `EMAIL_ONE_TIME_ACCESS_ENABLED` to `true` - restart pocket id - option is still disabled ### Expected behavior Changing the env values updates correctly the config in pocket-id ### Actual Behavior i updated an existing pocket-id instance and after the update i wanted to set the value `EMAIL_ONE_TIME_ACCESS_ENABLED` to `true`. After a restart, the option in the UI was still disabled. Then i thought, okay - maybe the key doesn't work and set it myself via the ui and set `PUBLIC_UI_CONFIG_DISABLED` back to `false` - restart, again nothing happened. I then changed the `SMTP_HOST` value as a test - worked, but the other values were not updated. Is there a problem? you can also set `Email Login Code from Admin` in the ui, but there doesn't seem to be an env key for this, or is this also controlled via `EMAIL_ONE_TIME_ACCESS_ENABLED`? ### Version and Environment version: 0.51.1 ### Log Output _No response_
OVERLORD added the bug label 2026-02-04 18:31:04 +03:00
OVERLORD commented 2026-02-04 18:31:15 +03:00
Author
Owner
Copy Link

@kmendell commented on GitHub (May 5, 2025):

This may be due to some naming changes we did to the settings, Ill try to take a look a bit later today :)

@kmendell commented on GitHub (May 5, 2025): This may be due to some naming changes we did to the settings, Ill try to take a look a bit later today :)
OVERLORD commented 2026-02-04 18:31:17 +03:00
Author
Owner
Copy Link

@stonith404 commented on GitHub (May 7, 2025):

The environment variables should now be up-to-date in the docs.

@stonith404 commented on GitHub (May 7, 2025): The environment variables should now be up-to-date in the docs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking
bug
bug
bug
documentation
feature
needs more upvotes
open to pull requests
pull-request
Mirrored from GitHub Pull Request
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#271
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?