Komodo & Multi-Scrobbler Config

[FestiveByteRider]

So before I begin just wanna say I actually discovered komodo through you so massive thanks for that and your migration guide was integral to my move, thanks a million for writing it. I've setup my music scrobbling stack inside komodo and am currently using an AIO.json config stored in the container's directory. I'm aware of the config file entry in the stack UI.

Is it possible to replace my current AIO.json with one managed by komodo and in UI so I can use interprelation for tokens etc and have easy backups? Apologies if this isn't the right place to ask I attempted to get info on the config file section in UI a few times in the discord and was unable to and the only thing I currently want it for is Multi-Scrobbler anyway. If there's somewhere else that's better suited for my question lmk and I'll go ask there instead. Thanks!!

[FoxxMD]

Hello and glad the komodo post helped you out!

so I can use interprelation for tokens etc

Just to clarify, I am under the impression that ENV interpolation, solely through komodo, only works for the default Environment. IE, using Variable interpolation like MY_FOO=[[MY_BAR]] only works within Environment (and not even in Additional Env Files). I might be wrong about that or something has changed in komodo v2, but that's how I thought that worked.

Now, you can do secret interpolation into config files directly through multi-scrobbler, but this uses plain environmental variables and is unrelated to komodo variable interpolation.

I borrowed the interpolation format from Komodo -- hopefully that isn't confusing -- but it's all pulled from ENVs at the container level. Example:

lastfm.json mounted into the CONFIG_DIR

[
  {
    "name": "myLastFmClient",
    "configureAs": "client",
    "data": {
      "apiKey": "[[MY_APIKEY]]",
      "secret": "[[MY_SECRET]]",
      "redirectUri": "http://localhost:9078/lastfm/callback"
    }
  }
]

services:
  multi-scrobbler:
    image: foxxmd/multi-scrobbler
    environment:
      - MY_APIKEY=foo
      - MY_SECRET=bar
    # ...
    volumes:
      - "./config:/config"

You could fill those ENVs using Komodo variables from the Environment section in a Stack, but regardless the end result needs to be environmental variables present in the container.

Is it possible to replace my current AIO.json with one managed by komodo and in UI

It is possible but I would not recommend it. Multi-scrobbler uses the mounted /config directory for reading config files and as persistent storage for credentials/caching. Depending on what Sources/Clients you are using you may not need any persistent storage (no credential data is generated) now but that is changing very soon with the introduction of a database.

If you use komodo's Config Files and the file/folder is managed by komodo (via git or ui-defined) then every time you re-deploy Komodo will wipe the folder and all the persisted data in it. Your aio config would be safe but everything else would be lost.

I will consider adding an ENV to enable specify a separate folder for persistent data but right now everything has to be in /config.

[FestiveByteRider]

So I tried out the config option and I was wondering do you know how the UI managed config file is provided to the container? I was left unaware if my container was actually getting the file and was hoping it'd show up in the docker config command and it unfortunately didn't.

[FoxxMD]

Just to be clear, you're talking about using a Git Repo Stack in Komodo and then editing a file via the Config Files section in the stack details page, right?

(As opposed to a UI Defined Stack in Komodo, which I don't think has Config Files at all.)

If it is the former: I believe all the Config Files section does is let you view/edit files that are already in your git repo. So it's still up to you to mount them into your stack using a relative directory IE Komodo doesn't do anything else for you WRT Config files other than letting you view/edit, there's no (magical/hidden) integration with the stack.

EX this is your repo structure:

.
├── multi-scrobbler <--- used as Run Directory for the komodo stack
│   ├── compose.yaml
│   └── myConfigs
│       └── config.json <--- your AIO config for MS
├── otherStackFoo
│   └── compose.yaml
└── otherStackBar
    └── compose.yaml

In your Git Repo Komodo stack:

• you set Run Directory to multi-scrobbler
• you manage the aio config via Config Files by adding it like myConfigs/config.json

In the resulting Info section on the Stack, where you manage the compose.yaml file for the Stack you'd need to do

services:
    multi-scrobbler:
      # ...
    volumes:
        # relative path from Run Directory : the mount point in the container
        - ./myConfigs/config.json:/config/config.json

I think that would be right, since komodo will run docker compose from the Run Directory you set for the stack.

[FestiveByteRider]

Oh right ok, to be honest that makes more sense and is more believable then my assumption. I assumed some computer magic was happening to provide it to containers. Well at least I know how the feature functions now I suppose. I'm gonna do some investigation and see if I can get the file to be stored on GitHub and be seen as stored at /config/config.json inside the container. If I find a solution would you be interested in what it is?

[FoxxMD]

I'm gonna do some investigation and see if I can get the file to be stored on GitHub and be seen as stored at /config/config.json inside the container.

I believe that the example compose I gave will work fine as-is for that exact scenario, given you commit the config file to the repo. That's not the real problem.

The issue is that MS creates other files for storing credential data and some cache files in /config.

If you only mount the config file like, ./myConfigs/config.json:/config/config.json, without any other mounts then all the additional files won't be persisted when you recreate the container (on a version update, for example).

AFAIK it's not possible to bind mount multiple host directories to the same directories within a container, without having one of them overwritten. IE

services:
    multi-scrobbler:
      # ...
    volumes: # won't work?
        -  /some/persistent/dir:/config
        - ./myConfigs/config.json:/config/config.json

I think depending on the order, either config.json won't show up or the folder won't show up. Unless you do some magic trickery with overlayfs like this.

Maybe it can be done with a named volume and then bind mounting in the config? idk.

If you figure out to get all of that work definitely report back.