Hi all, I’m new to Meltano. Following the getting ...
# troubleshooting
d
Hi all, I’m new to Meltano. Following the getting started documentation using docker to generate my project and install some plugins I noted, that the working directory in the examples is not the same: projects vs project. Could that be a potential problem if I accidentally mix up working directories?
Another point, if I add the docker file with
meltano add files docker
the docker file itself uses the working directory project
a
Hi @delbert_friesen! This is something we should fix in our docs, but it’s not going to be a problem. In the first example, we are mounting the current directory (
$(pwd)
) as
/projects
in the Docker container, and then setting the same
/projects
as the working directory. In the second example, it’s
/project
instead. Since we start a new container with each
docker run
command, it doesn’t really matter if we use
/projects
or
/project
. We just need to make sure that the directory names match in the
docker run
command.
Another point, if I add the docker file with
meltano add files docker
the docker file itself uses the working directory project
This depends on which Docker container you are running this command in. If you are running this command in the container that was started using the second command which uses
/project
as the working directory, then that’s the directory that will be used.
This is something we should fix in our docs, but it’s not going to be a problem.
Looking at this again, in the first command, we are creating a new Meltano project inside our “projects” directory. It’s then semantically reasonable that we mount the directory as
/projects
. However, the second command is being executed from within the newly created Meltano project directory, that’s why that directory is mounted as
/project
. Just good naming practices I think. We second command can also be written as below to be slightly more clear:
Copy code
docker run -v "$(pwd)":/yourprojectname -w /yourprojectname -p 5000:5000 meltano/meltano