#musicbrainz

I am trying to set my token for the replication but I am doing it wrong :

docker-compose exec musicbrainz .\admin\set-replication-token.sh mysecrettokenhere

OCI runtime exec failed: exec failed: unable to start container process: exec: ".\\admin\\set-replication-token.sh": executable file not found in $PATH: unknown

that's referencing a path inside the container rather than one on the host, so try using forward slashes instead

I have the same issue with : C:\dev\musicbrainz-docker> docker-compose exec musicbrainz ./admin/set-replication-token mysecrettoken

my bad, that script is actually meant to run on the host, which means you should remove the whole "docker-compose exec musicbrainz" part

also, it reads your token from stdin, I don't think you can pass it as an argument

C:\dev\musicbrainz-docker> ./admin/set-replication-token just open the file

it's a bash script so I'm not sure how to run that on windows, tbh

alternatively you can just save the token to local/secrets/metabrainz_access_token (under the musicbrainz-docker repo), since that's all the script does

i cannot see, under windows or powershell the secrets folder

you may have to create it

i have created this file, with my token inside, but the LoadReplicationChanges failed because : Invalid or missing REPLICATION_ACCESS_TOKEN in DBDefs.pm

there was another step you had to do in the README, but it's also a bash script. let me see what it does

I have tried to change DBDefs.pm to have

sub REPLICATION_ACCESS_TOKEN {"mysecrettoken"}, but I still have the same error

do you have an .env file in the musicbrainz-docker directory?

nope

try creating one with COMPOSE_FILE=docker-compose.yml:compose/replication-token.yml

then apparently you have to run `docker-compose up -d` again

I do not understand the COMPOSE_FILE=   ; mayvbe it'ss working on Linux, but i have an error on windows with that

to be clear that's the contents of the .env file you need to create, not a command

ha ^^

did you change DBDefs.pm in the host repository, or inside the container? I would also revert your changes in case it conflicts with this

i have reverted my change in the DBDef

ok

i have created the env file and have a new error :

docker-compose exec musicbrainz replication.sh

CreateFile C:\dev\musicbrainz-docker\docker-compose.yml:compose\replication-token.yml: La syntaxe du nom de fichier, de répertoire ou de volume est

incorrecte.

(i'm french)

i have delete the env file and this error is no more here, but still have the token issue

hmm

yes there is something strange

my bad, I think windows uses a different path separator for COMPOSE_FILE - https://docs.docker.com/compose/environment-var...

try creating the .env file again, but with COMPOSE_FILE=docker-compose.yml;compose/replication-token.yml

; separating the files instead of :

i do not have the error anymore indeed

but still have the token issue

did you run `docker-compose up -d` again?

oups ^^

i did still have an issue but not the same !

docker-compose exec musicbrainz /usr/bin/tail -f mirror.log    give me some info about Client-SSl and finishes with : Provided access token is invalid!

but i have not provided my token at all

sorry, the token is in the musicbrainz-docker\local\secrets\metabrainz_access_token file

it's OK !

i have generated a new token and it's ok

so replication is working now? :)

I'll try to make progress with the data update, and I'll keep you updated."

i will try it now

i do not want a "live replication"  but i want to type a comand line to have the last replication packet, i will follow the doc ^^

i am confused because there is nothing more to do haha :D

there is no output in the command line to tell us where we are ? (i actually do a refresh on the http://localhost:5000/  and check the footer

lol are you following the "Run replication once" section?

yes but i have just type : C:\dev\musicbrainz-docker> docker-compose exec musicbrainz replication.sh    not the "log part"

ah, well the log file will show you the current progress

i am seeing that :)

when it's up to date, the script ends ? or if we do not touch anything, it keeps you up to date ?

it will run in the background until it reaches the latest available packet, then it exits. so if you want to update the DB again, you have to re-execute the command

it sounds like that's what you wanted?

ok, perfect. I jsut want to be up to date when i desire

yes exactly !

cool, you're all set then

yes ! thanks a lot

you're welcome :)

I have a last question

on a release-group, at the end of the right column, you can see the "Last updated on "

Is this information provided by the API ? thanks to https://musicbrainz.org/ws/2/release-group/fa56... for example

no it's not, although this only indicates when the row in the release_group table was updated. it doesn't get updated when any associated data changes (aliases, tags, releases, etc.)

that's why i do not see this date changes  ^^

ok a big thnaks for your time bitmap

thanks*