Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stable to use on main server? #8

Closed
BLACK4585 opened this issue Feb 27, 2024 · 2 comments
Closed

Stable to use on main server? #8

BLACK4585 opened this issue Feb 27, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@BLACK4585
Copy link

Hey, I just stumbled across your fork. You wrote that we should not mess with the main server config when using the Segments API. Is it unsafe to use? What are the possible things that could happen?
I'm interested since I want to use this plugin and aren't sure if it's already stable enough for the main server.
Also, I really need your patched Jellyfin version?

@BLACK4585 BLACK4585 added the enhancement New feature or request label Feb 27, 2024
@jumoog
Copy link

jumoog commented Mar 2, 2024

Also, I really need your patched Jellyfin version?

Yes, you do. Otherwise the plugin won't work.

@endrl
Copy link
Owner

endrl commented Mar 15, 2024

What are the possible things that could happen?

The database migration won't be compatible with the migration that will be merged into stable jellyfin. You need to delete the table and index when you switch back with a sqlite editor.

But you shouldn't do it, as you need also official client support. Read more here: #4 (comment)

@endrl endrl closed this as completed Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants