Skip to content

Feature/replace_overseerr_and_jellyseerr_with_seerr#83

Merged
Luctia merged 5 commits into
Luctia:mainfrom
inebriatedfinish:feature/replace_overseerr_and_jellyseerr_with_seerr
Jun 23, 2026
Merged

Feature/replace_overseerr_and_jellyseerr_with_seerr#83
Luctia merged 5 commits into
Luctia:mainfrom
inebriatedfinish:feature/replace_overseerr_and_jellyseerr_with_seerr

Conversation

@inebriatedfinish

@inebriatedfinish inebriatedfinish commented Jun 21, 2026

Copy link
Copy Markdown
Contributor

Background

The Overseerr and Jellyseerr projects have been merged into one project now called "Seerr". This means the currently used Overseerr and Jellyseerr containers unmaintained.

Scope

This would only replace the manual install steps with the new Seerr application. I am more well versed with shell scripts than Python so I thought that would be an easier start. From what I could tell, the python scripts do not rely on any files used in the manual installation (Correct me if I'm wrong here).

Changes

  • Based on the Seerr migration documentation, they recommend to use the container's default UID and GID. (See link and link)
  • Replace all Overseerr items with Seerr
  • Remove all Jellyseerr items
  • I didn't remove Overseerr and Jellyseer from the remove_old_users.sh script since I wasn't sure if they should be kept for legacy users.

- Remove overseer and jellyseer variables and
  replace with a "seerr" variable.
- Am not currently using the variable since the
  seerr documentation recommends using the default
  UID and GID of the container image.

feature/replace_overseer_and_jellyseer_with_seerr
- Overseerr and Jellyseerr have been combined into
  "Seerr". Both Overseerr and Jellyseerr are no
  longer maintained.
- Removes Overseerr and Jellyseerr from docker
  compose
- Adds Seerr to docker compose with guidance from
  official documentation.

feature/replace_overseerr_and_jellyseerr_with_seerr
I did not remove Overseerr and Jellyseer yet since
people may still have those users if they used the
script before this update.

feature/replace_overseerr_and_jellyseerr_with_seerr
- Seerr does not recommend using a non-default UID
  and GID and the defaults are 1000:1000 so I
  updated the Seer config folder to use those
  permissions.
- Technically since the current user is added to
  the "mediacenter" and most likely this will be
  the default user the person used to setup linux
  with the permissions 1000:1000, the mediacenter
  group could likely be used. It's not good to
  make assumptions though.

feature/replace_overseerr_and_jellyseerr_with_seerr
- There is no "Seerr" user created, so there is no
  need to "delete" that user either.
@inebriatedfinish inebriatedfinish marked this pull request as ready for review June 21, 2026 02:48

@Luctia Luctia left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit hesitant to use the default user ID for this container but if they say it's the best way to use it, I'm inclined to trust them. Looks good otherwise, thanks for the work!

@Luctia Luctia merged commit 32e1dfa into Luctia:main Jun 23, 2026
1 check passed
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