Unclear documentation wording: "not on subsequent launches using the same configuration database."

[kasir-barati]

Thanks for your commitment to this project and keeping its documentation up to date. I am currently trying to map a servers.json and preferences.json into pgadmin. So I was reading your doc and I kinda read it several times but did not manage to wrap my head around it. What does it mean by subsequent launches?

In docker personally just delete the containers in dev env and start them again. (docker compose down -v, and then docker compose up -d). So it kinda bugged me and since my mapping is not working right now (this is I guess a different matter, I'm mapping some files from my host into docker container but for some reason it does not map them at all :/) I was not able to verify what will happen if I:

• Remove the containers and start fresh.
• Just recreate the container by running docker compose up -d again after the first time.

Thus I am suggesting to rephrase or add a bit more details in these two places:

• https://github.com/pgadmin-org/pgadmin4/blob/b2782650055dd41c060cd016f29ecd5575cd1828/docs/en_US/container_deployment.rst?plain=1#L233-L237
• https://github.com/pgadmin-org/pgadmin4/blob/b2782650055dd41c060cd016f29ecd5575cd1828/docs/en_US/container_deployment.rst?plain=1#L241-L245

And "using the same configuration database" did not help me at all.

[kasir-barati]

BTW for those who are wondering what I did with my issue regarding pgadmin not mapping (binding) my servers.json, eventually I gave up on the idea of having a separate file and used the same compose.yaml file as here: https://stackoverflow.com/a/77519799/8784518

[kasir-barati]

On another note I also realized that for some reason it won't pick up on my customization in preferences.json. But I confirmed that there is a file called preferences.json inside /pgadmin4. And I am sure it has docker has nothing to do with what is described here since the doc about /pgadmin4/preferences.json is clear about the fact that if you have this file in the aforementioned path then it'll automatically customize your work env.

You can reproduce the issue with instruction provided here: https://github.com/kasir-barati/docker/tree/main/docker-compose-files/postgres/postgres-pgadmin