Docker-Compose example of both Sync and Watch running under same service?

[xInsertx]

Hi,

I was wondering if anyone could provide an example of 2 separate containers running under the same docker-compose for the sync and scrobble tasks respectively.

The idea would be to interactively set-up the credentials / etc then share the same volume/bind-mount. I am able to get one or the other running - but not both at the same time.

The intent was to replace the old plex-style plugin functionality.

edit: can someone also confirm what location/path the auth info gets saved? doesn't seem to be in the config dir (useless it's in the sqlite db?)

[glensc]

and then why don't you share your attempt?

[xInsertx]

@glensc Sorry for the late reply - just been busy. I ran the following compose to generate the containers - then "docker run interactive " the sync container to get it set-up. I plan to fiddle with this more over the weekend.

I found the json files with the tokens etc after /bin/sh into the container. Is there a current 'recommend' on if 2 processes are running (assuming same user) should we read-only the mount or specific file on the 'watch' container?

Note: No scheduler is included because post testing ill let kube-scheduler worry about it (I prefer to test on stand-alone docker before importing to kube)

My intent is to get a template so I can pipe things to a script (until/if multi-user support is added) to build for additional users.

As a separate quick question - is there anything stopping me from generating the .json outside and mounting it (if I had the info already and want to map additional users) or would this be better suited via passing environmental variables?

services:
  sync:
    image: ghcr.io/taxel/plextraktsync:latest
    container_name: plexts-sync
    volumes:
      - /path/to/bind/config:/app/config
  watcher:
    image: ghcr.io/taxel/plextraktsync:latest
    container_name: plexts-watcher
    volumes:
      - /path/to/bind/config:/app/config
    command: watch

[glensc]

your compose file seems fine. you may want to do one-time login command to generate the credential files:

docker-compose run --rm sync login

I don't understand anything from rest of your text, sorry. too specific text assuming I know what are you doing. but I don't.

[stunrelay]

@glensc Sorry for the late reply - just been busy. I ran the following compose to generate the containers - then "docker run interactive " the sync container to get it set-up. I plan to fiddle with this more over the weekend.

I found the json files with the tokens etc after /bin/sh into the container. Is there a current 'recommend' on if 2 processes are running (assuming same user) should we read-only the mount or specific file on the 'watch' container?

Note: No scheduler is included because post testing ill let kube-scheduler worry about it (I prefer to test on stand-alone docker before importing to kube)

My intent is to get a template so I can pipe things to a script (until/if multi-user support is added) to build for additional users.

As a separate quick question - is there anything stopping me from generating the .json outside and mounting it (if I had the info already and want to map additional users) or would this be better suited via passing environmental variables?

services:
  sync:
    image: ghcr.io/taxel/plextraktsync:latest
    container_name: plexts-sync
    volumes:
      - /path/to/bind/config:/app/config
  watcher:
    image: ghcr.io/taxel/plextraktsync:latest
    container_name: plexts-watcher
    volumes:
      - /path/to/bind/config:/app/config
    command: watch

I’ve also been curious about running both watch and sync simultaneously. Seems like the only solution atm is to run 2 separate instance containers and run the sync container on a schedule. Did your compose work? Or did you have to do extra fiddling…

[glensc]

yes, you can copy and mount the files in config dir created anywhere else. the pytrakt module may want to update the .pytrakt.json file any time it finds refresh token needs to be done, so better not mount it readonly or you be eventually locked out as token will expire.

ps: I still don't understand what are you doing and those tools and terminology you say. too specific.