It seems this page misses one critical piece of info - which repo(s) to clone to get started. It talks about locally available code as a given.
Topic on Talk:Wikibase/Docker
Appearance
The process doesn't involve cloning a git repo. Under Wikibase/Docker#Preparing your environment you'll see instructions to examine and modify the example files, which you will then use with Docker to launch your instance.
@Dan Shick (WMDE) I saw that -- but that doesn't explain from which files one should start! I.e. given a blank slate, which git repo should i clone, or which files should I create and where to get to the running state. I could run "docker run ..." to get some container running, but the moment you switch to docker-compose, one should probably have some local config files, or possibly a locally modified clone of some repo.
Please refer to the "Before you start" section. The process relies on your familiarity with docker-compose to recognize how to use the docker-compose.yml file in the examples directory. The instructions that follow explain how to modify that file.
@Dan Shick (WMDE) I have used docker-compose for many years. My point is about those files - should I just copy that one file from the example directory? Should I clone the whole repo and just use that one dir?
Glad to hear you're familiar with docker-compose. As the instructions indicate, you should use the example docker-compose.yml file, the template.env file, and, optionally, the docker-compose-extra.yml file, customized for your own install.
The docs take their time explaining things in detail -- our intention is not to provide ready-to-run docker-compose files, but to explain to experienced users such as yourself how to construct your own based on our examples.
Came here with the same question. The docs could need some work.