Skip to content

Conversation

@M0NsTeRRR
Copy link
Member

Description

add migration guide

@M0NsTeRRR M0NsTeRRR requested a review from a team as a code owner October 18, 2025 20:49
@M0NsTeRRR M0NsTeRRR marked this pull request as draft October 18, 2025 20:49
@github-actions
Copy link

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

@github-actions github-actions bot added the merge conflict Cannot merge due to merge conflicts label Oct 19, 2025
@Gylesie
Copy link
Contributor

Gylesie commented Oct 19, 2025

This guide is low value for users with existing Jellyseerr and Overserr instances. It essentially tells them to scratch whatever they had previously in e.g. docker compose and replace it with whatever is in the general getting started guide which is geared towards new users.

@M0NsTeRRR M0NsTeRRR force-pushed the docs/migration-guide branch from 3d0a373 to bdbccfb Compare October 19, 2025 17:20
@github-actions github-actions bot removed the merge conflict Cannot merge due to merge conflicts label Oct 19, 2025
@M0NsTeRRR
Copy link
Member Author

This guide is low value for users with existing Jellyseerr and Overserr instances. It essentially tells them to scratch whatever they had previously in e.g. docker compose and replace it with whatever is in the general getting started guide which is geared towards new users.

  1. It’s still in draft, I need to confirm whether additional migration steps are required.
  2. This is for users with less experience, and it’s meant to prevent support tickets like, 'Is it really as easy as updating the Docker image reference?' This way, we can simply redirect them here. Users with more experience already know how to handle the new image and what it does for them.

@Gylesie
Copy link
Contributor

Gylesie commented Oct 19, 2025

I understand its in draft, but you requested a review. So thats why I wanted to give some feedback.

I just dont find it helpful overall. It literally says to replace the whole compose file with new one. But there is a good chance that the user is running different services in a single compose file. What should they do then?

I dont think majority of users would need this much hand holding to migrate. Showing an example of an old docker compose file and then the new one with specific changes that were made highlighted would be better.

@M0NsTeRRR M0NsTeRRR mentioned this pull request Oct 30, 2025
38 tasks
@M0NsTeRRR M0NsTeRRR marked this pull request as ready for review October 30, 2025 22:39
@M0NsTeRRR M0NsTeRRR force-pushed the docs/migration-guide branch from 41c8f24 to a140077 Compare October 31, 2025 15:42
Copy link
Member

@gauthier-th gauthier-th left a comment

Choose a reason for hiding this comment

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

LGTM

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.

7 participants