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

Feature request: Multi-User Support #629

Closed
JonzaUK opened this issue Dec 7, 2021 · 12 comments
Closed

Feature request: Multi-User Support #629

JonzaUK opened this issue Dec 7, 2021 · 12 comments
Labels
docs needed Changes in this issue/pull request need to be documented enhancement New feature or request

Comments

@JonzaUK
Copy link

JonzaUK commented Dec 7, 2021

Feature description

Use case

Ability to have multiple plex users to sync there watched status etc to trakt accounts... e.g:

Plex User 1 -> Sync to Trakt User 1
Plex User 2 -> Sync to Trakt User 2

I'm sure you get the idea.

Workarounds

Not that I'm aware... (currently using the old Trakt4Plex plugin within Plex - but been looking for an alternative since Plugins were deprecated (even though they still work for now)

@JonzaUK JonzaUK added the enhancement New feature or request label Dec 7, 2021
@glensc
Copy link
Collaborator

glensc commented Dec 9, 2021

Workarounds: Not that I'm aware...

Not sure if i understand correctly, but workaround is very simple: you setup multiple installations of plextraktsync.

@glensc
Copy link
Collaborator

glensc commented Dec 12, 2021

@JonzaUK please clarify!

@rfgamaral
Copy link

Not sure if i understand correctly, but workaround is very simple: you setup multiple installations of plextraktsync.

I believe they are asking for PlexTraktSync to support multiple user authentications (both on Trakt and Plex), and, perhaps, have different sync settings for each one of them.

@glensc
Copy link
Collaborator

glensc commented Dec 12, 2021

But then workaround exists: run multiple PlexTraktSync installations (instances) with different configs

@rfgamaral
Copy link

But then workaround exists: run multiple PlexTraktSync installations (instances) with different configs

Yes, I know. And it's easier to set it up with Docker. But for people not using Docker, it would be much easier if PlexTraktSync supported this out-of-the-box. I'm just saying, I don't need multi-user support myself.

@glensc
Copy link
Collaborator

glensc commented Dec 12, 2021

It's not about knowing or not, but feedback to the issue body "Workarounds: Not that I'm aware... " that's why I wanted to clarify with the issue author.

@rfgamaral
Copy link

I think it's safe to assume that they aren't aware that they could just set up multiple instances of PlexTraktSync.

@JonzaUK
Copy link
Author

JonzaUK commented Dec 12, 2021

Hi Everyone,

Apologies, didn't even think about multiple instances... yes this would work for multiple users... not practical for my use, I have around x12 family members around 10x of which all have Trakt accounts... so setting up 10x instances is a bit of a pain though would work... I think just having Multiple user support built in is a more elegant solution, at the moment using the Plugin I just configure everyone user and trakt account in the one plugin... I would assume having multi-user support would be more resource friendly then running 10x docker instances.

@glensc
Copy link
Collaborator

glensc commented Dec 12, 2021

Please explain the "pain", to me it's "pain" to maintain extra code to support extra functionality that can be easily be done outside this project.

@joggs
Copy link

joggs commented Dec 16, 2021

Workarounds and pain to maintain code. Wow. sounds like a dying project

@glensc
Copy link
Collaborator

glensc commented Dec 16, 2021

Closing and locking due to unwanted attitude.

@glensc glensc closed this as completed Dec 16, 2021
Repository owner locked as too heated and limited conversation to collaborators Dec 16, 2021
@simonc56
Copy link
Collaborator

You can use the environment variable PTS_CONFIG_DIR and change it before each run to use a specific folder for each user.

Repository owner unlocked this conversation Dec 17, 2021
@glensc glensc added the docs needed Changes in this issue/pull request need to be documented label Jan 7, 2022
Repository owner locked as resolved and limited conversation to collaborators Jan 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
docs needed Changes in this issue/pull request need to be documented enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants