Multi-User docker-compose

[Anon0511]

Here is a docker-compose for syncing multiple users, thus running multiple instances, in my case 21 users. I just trashed it together and don't guarantee it to be best practice. Maybe you want to provide it as an example docker-compose.yml in the Git Repo?

Have a nice day!

version: '3.7'
services:
  plextraktsync: &default
    image: ghcr.io/taxel/plextraktsync
    container_name: plextraktsync
    restart: on-failure:2
    volumes:
      - /home/plextraktsync:/app/config
    networks:
      - plex

  plextraktsync1:
    <<: *default
    container_name: plextraktsync1
    volumes:
      - /home/plextraktsync1:/app/config

  plextraktsync2:
    <<: *default
    container_name: plextraktsync2
    volumes:
      - /home/plextraktsync2:/app/config

  plextraktsync3:
    <<: *default
    container_name: plextraktsync3
    volumes:
      - /home/plextraktsync3:/app/config

  plextraktsync4:
    <<: *default
    container_name: plextraktsync4
    volumes:
      - /home/plextraktsync4:/app/config

  plextraktsync5:
    <<: *default
    container_name: plextraktsync5
    volumes:
      - /home/plextraktsync5:/app/config

  plextraktsync6:
    <<: *default
    container_name: plextraktsync6
    volumes:
      - /home/plextraktsync6:/app/config

  plextraktsync7:
    <<: *default
    container_name: plextraktsync7
    volumes:
      - /home/plextraktsync7:/app/config

  plextraktsync8:
    <<: *default
    container_name: plextraktsync8
    volumes:
      - /home/plextraktsync8:/app/config

  plextraktsync9:
    <<: *default
    container_name: plextraktsync9
    volumes:
      - /home/plextraktsync9:/app/config

  plextraktsync10:
    <<: *default
    container_name: plextraktsync10
    volumes:
      - /home/plextraktsync10:/app/config

  plextraktsync11:
    <<: *default
    container_name: plextraktsync11
    volumes:
      - /home/plextraktsync11:/app/config

  plextraktsync12:
    <<: *default
    container_name: plextraktsync12
    volumes:
      - /home/plextraktsync12:/app/config

  plextraktsync13:
    <<: *default
    container_name: plextraktsync13
    volumes:
      - /home/plextraktsync13:/app/config

  plextraktsync14:
    <<: *default
    container_name: plextraktsync14
    volumes:
      - /home/plextraktsync14:/app/config

  plextraktsync15:
    <<: *default
    container_name: plextraktsync15
    volumes:
      - /home/plextraktsync15:/app/config

  plextraktsync16:
    <<: *default
    container_name: plextraktsync16
    volumes:
      - /home/plextraktsync16:/app/config

  plextraktsync17:
    <<: *default
    container_name: plextraktsync17
    volumes:
      - /home/plextraktsync17:/app/confi0g

  plextraktsync18:
    <<: *default
    container_name: plextraktsync18
    volumes:
      - /home/plextraktsync18:/app/config

  plextraktsync19:
    <<: *default
    container_name: plextraktsync19
    volumes:
      - /home/plextraktsync19:/app/config

  plextraktsync20:
    <<: *default
    container_name: plextraktsync20
    volumes:
      - /home/plextraktsync20:/app/config

  scheduler: &default1
    image: mcuadros/ofelia:latest
    container_name: scheduler
    depends_on:
      - plextraktsync
    command: daemon --docker
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    labels:
      ofelia.job-run.plextraktsync.schedule: "@every 6h"
      ofelia.job-run.plextraktsync.container: "plextraktsync"

  scheduler1:
    <<: *default1
    container_name: scheduler1
    depends_on:
      - plextraktsync1
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync1"

  scheduler2:
    <<: *default1
    container_name: scheduler2
    depends_on:
      - plextraktsync2
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync2"

  scheduler3:
    <<: *default1
    container_name: scheduler3
    depends_on:
      - plextraktsync3
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync3"

  scheduler4:
    <<: *default1
    container_name: scheduler4
    depends_on:
      - plextraktsync4
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync4"

  scheduler5:
    <<: *default1
    container_name: scheduler5
    depends_on:
      - plextraktsync5
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync5"

  scheduler6:
    <<: *default1
    container_name: scheduler6
    depends_on:
      - plextraktsync6
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync6"

  scheduler7:
    <<: *default1
    container_name: scheduler7
    depends_on:
      - plextraktsync7
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync7"

  scheduler8:
    <<: *default1
    container_name: scheduler8
    depends_on:
      - plextraktsync8
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync8"

  scheduler9:
    <<: *default1
    container_name: scheduler9
    depends_on:
      - plextraktsync9
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync9"

  scheduler10:
    <<: *default1
    container_name: scheduler10
    depends_on:
      - plextraktsync10
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync10"

  scheduler11:
    <<: *default1
    container_name: scheduler11
    depends_on:
      - plextraktsync11
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync11"

  scheduler12:
    <<: *default1
    container_name: scheduler12
    depends_on:
      - plextraktsync12
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync12"

  scheduler13:
    <<: *default1
    container_name: scheduler13
    depends_on:
      - plextraktsync13
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync13"

  scheduler14:
    <<: *default1
    container_name: scheduler14
    depends_on:
      - plextraktsync14
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync14"

  scheduler15:
    <<: *default1
    container_name: scheduler15
    depends_on:
      - plextraktsync15
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync15"

  scheduler16:
    <<: *default1
    container_name: scheduler16
    depends_on:
      - plextraktsync16
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync16"

  scheduler17:
    <<: *default1
    container_name: scheduler17
    depends_on:
      - plextraktsync17
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync17"

  scheduler18:
    <<: *default1
    container_name: scheduler18
    depends_on:
      - plextraktsync18
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync18"

  scheduler19:
    <<: *default1
    container_name: scheduler19
    depends_on:
      - plextraktsync19
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync19"

  scheduler20:
    <<: *default1
    container_name: scheduler20
    depends_on:
      - plextraktsync20
    labels:
      ofelia.job-run.plextraktsync.container: "plextraktsync20"

networks:
  plex:
    external: true

[ghost]

Hey I am just curious to know one thing before I dive into this section. I am completely new to this docker container thing and would like to know few answers to check whether it suits my need or not? So first of all, I have several users on my plex media server running on latest Ubuntu server. If I am going with this approach, do I need to create separate plex instances as well or just running this plextraktsync with their numbers would work for me? I am trying to automate everything I am doing with shell script and but I am not sure how containerisation will work and most importantly taking all these efforts worth the shot or not? I mean no offence this system is best but on my end whether it requires to be automated or just a manual check in would be fine is to be evauluated before I dive deeper in this project.

[Anon0511]

Hey,

only one Plex instance is needed. And also only one Trakt user is needed. You can sync all Plex users histories to a single Trakt user.

[thobi85]

Hi,
thanks for the script.
So if I got it right you set up for every plex user a seperate docker.
How and where do you specify the user for docker?
I didn't find anything in the config file, just the username_filter criteria.

regards

[Anon0511]

No, everything will be in a single Trakt user, with a single list at the end. So it depends on the usecase. I have tons of collections in Plex made with Plex-Meta-Manager. So in my case plextraktsync is only used to feed https://couchmoney.tv/ and the generated lists are added to Radarr and Sonarr to fill them up with more media that my users might like but is not added yet.

Also there are many features that won't work this way or rather said you shouldn't use or else you break your users Plex experience (https://github.com/Taxel/PlexTraktSync#features). There shouldn't be anything from Trakt synced back to Plex.

Else you need one Trakt account per Plex user.

[thobi85]

Sounds quite similiar what I would like to do.
I have plex-meta-manager, Couchmoney and would like to have specific recommendations lists/collections for each user.

But with one single history list it would not be possible to have seperate recommendations, because trakt don't know which user has watched it or?

[Anon0511]

Exactly.

[amacomber]

Does this work for syncing multiple Plex users to their respective Trakt accounts? Or is this only for the Plex owner to sync to multiple Trakt accounts?

[Anon0511]

This basically is a good question and at the current state I have no idea anymore. I'm not affiliated to this project at all, just a user as well and just checking through all my plextraktsync containers to add a new user, I found them all stopped working. When I ran a plex-login I was only able to chose my own and another "Home" account but none of the external accounts from my users. So I"m a bit behind of what has changed or if it is bugged or what the issue is.

But basically it was possible to sync any user from your server to any Trakt account you wanted if you had the App-OAuth details (Client-ID and Client-Secret).

[SawkeeReemo]

With this compose, does that make each container run one after the other? Or will they all launch simultaneously every six hours?

[Anon0511]

All simultaneously considering the set cronjob interval in each scheduler using the set default of ofelia.job-run.plextraktsync.schedule: "@every 6h". Reading the ofelia Repo it says: [Scheduling format](https://godoc.org/github.com/robfig/cron) is the same as the Go implementation of cron. E.g. @every 10s or 0 0 1 * * * (every night at 1 AM).
So you surely can set the Cron Format and accordingly play with the minutes section.
To achieve what you mentioned, running one after the other Independent of timeflags, I can only think of a bash script and removing all the ofelia stuff in the compose and also removing restart:. Then having the script start at host cron intervals, start 1, wait (will hold and wait for exit code), start 2 and so on.

[stevezau]

Posting this little script here in case it helps anyone else #2049

[stevezau]

@Anon0511 how did you set the config for each user without logging in as each user? In other words what does your user config look like to only sync that plex user watch status to trakt

[Anon0511]

I'm sorry I'm replying that late.
Well, this contribution was from before that said change. Since this was a privacy change from Plex side, there is probably not much we can do or blame the App about. But the result however is indeed that you'd need the login data of everyone which is just ridiculous. I soon after dropped the usage of it and started lurking around for Tautulli things and I can tell you that there is indeed a script for Tautulli which one could use to send all watched episodes to Trakt. However it didn't work well for me with multiple Plex Servers and thus multiple Tautullis but this might be useful for some others tho.