-
-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Description
π Bug Description
Hello, Im running List-sync on Docker-compose and noticed that the default Overseer user that I gave in env is not set and instead the default userid 1 is chosen. I have checked in the UI as well as entering the container and checking the env. Both show the userID as 3 but when i check the lists on dashboard it shows user 1.
Tried restarting and refreshing the user list in configuration but did not help.
For Reference added my docker compose
image: ghcr.io/woahai321/list-sync:0.6.6
container_name: listsync
environment:
- TZ=${TIMEZONE}
- "OVERSEERR_URL=http://jellyseerr:5055"
- "OVERSEERR_API_KEY=${OVERSEERR_API_KEY}"
- "OVERSEERR_USER_ID=3"
#- OVERSEERR_USER_ID=${OVERSEERR_USER_ID:-1}
- SYNC_INTERVAL=${SYNC_INTERVAL:-1}
- RUNNING_IN_DOCKER=true
- AUTOMATED_MODE=true
- TRAKT_CLIENT_ID=${TRAKT_CLIENT_ID} # trakt client secret not needed
- OVERSEERR_4K=${OVERSEERR_4K:-false}
- "IMDB_LISTS=${IMDB_LISTS}"
#- TRAKT_LISTS=${TRAKT_LISTS}
#- "LETTERBOXD_LISTS=${LETTERBOXD_LISTS}"```
### π Expected Behavior
Listsync should choose the userid 3 for overseer requests as set in ENV as well as dashboard and not set userid 1 for individual lists
### β Actual Behavior
Lists are set with userid 1
### π Steps to Reproduce
Use my docker compose by replacing the secrets then look at dashboard. Check Lists tab and notice user under each list & compare it with env
### π» Operating System
Other Linux
### π§ Installation Method
Docker
### π¨ Error Messages
```shell
No error in logs
π οΈ Affected Areas
- Synchronization
- User Interface
- Data Processing
- Configuration
- Performance
- Other (specify in additional context)
π Relevant Log Entries
βοΈ Configuration
π Additional Context
Previously I was running v0.6.2 and it was working correctly. I'm seeing this issue after directly upgrading to the latest version
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels