Config not taking effect and not showing in console

Local Setup
1

1- I followed the docker setup: Docker Compose - Heroic Labs Documentation

it says: You must edit the nakama:volumes: entry in your docker-compose.yml file so that it looks like the following: /c/Users/<username>/projects/docker:/nakama/data.

2- followed the config setup: Server Configuration - Heroic Labs Documentation

it says: Edit the nakama:volumes: entry to specify your desired volume. For example, to create a /data folder in our desktop/nakama directory used above, which would be available at nakama/data in your Docker container (reverting what it said in the setup above). so final result is:

volumes:
      - ./data:/nakama/data

3- but in config.yml I used only:

socket:
  server_key: testServerKey

4- Open your docker-compose.yml file again, this time to edit the nakama:entrypoint entry to add the --config flag pointing to your configuration file. It should look like this: edited to add this /nakama/nakama --config /nakama/data/config.yml. the final entry looks like:

entrypoint:
      - "/bin/sh"
      - "-ecx"
      - >
          /nakama/nakama migrate up --database.address postgres:localdb@postgres:5432/nakama &&
          exec /nakama/nakama --name nakama1 --database.address postgres:localdb@postgres:5432/nakama --logger.level DEBUG --session.token_expiry_sec 7200 &&
          /nakama/nakama --config /nakama/data/config.yml

the end result is that the console is still showing the default config values.

also when I export the console config, edit the keys I want then try to pass it by calling /nakama/nakama --config /nakama/data/config.yml in shell, I get errors that it failed to ping the postgres db. and also many of the values are redacted or invalid (the party entry is null and I get an error to add some missing values)

What is the easiest way to edit the config? I jsut want to update the server key.

  1. Versions: Nakama {3.5}, {Windows, Mac, Linux binary or Docker}, {client library (SDK) and version}
  2. Server Framework Runtime language (If relevant) {Go, TS/JS, Lua}
{code or log snippet}

:tv: Media:

2

the issue was in my entry point, solved by this comment.