Update instapy-docker to remove xpath_compile.py dependency #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello all
In past days it was asked to update
xpath_compile.py
due to some changes in InstaPy (repo #5895 and #5899),the change was requested because of the dependencies between InstaPy-Docker and InstaPy.
It means, that if some one changes or modify
InstaPy - xpath_compile.py
then the same change needs to be propagated toInstaPy-Docker - xpath_compile.py
because of the Dockerfile copy the file to the Docker image.On the other hand, if someone ( like I did :p ) proactively changes the Instapy-Docker
xpath_compile.py
with the latest changes it will cause the Docker image to fail since internally there are parts that still cannot consume the new xpaths.https://hub.docker.com/r/instapy/instapy/dockerfile
needs to be updated to reflect the changes in the new Dockerfile, if this PR is approved.We could say that it is a game of cat and mouse, where it is changed first in a repository and the failure of the second, or the second repository is modified and the failure of the first is expected.
I created this PR to remove the
xpath_compile.py
dependency, so the user can always runInstaPy-Docker
without the urgency of checking if the xpath_compile is the correct one. I ran several timesInstaPy-Docker
with Docker-Compose and Dockerfile and never hit the issue mentioned in #4877.I believe that a WA over how to start the Docker image is better if the user hit the same issue for extra characters like (```) or different xpath values; I have the impression that docker users know how to get around this type of configuration.
ie:
they can just map the correct xpath_compile directly from console, this way the changes can be done on the fly.
-v $(pwd)/xpath_compile.py:/usr/local/lib/python3.7/site-packages/instapy/xpath_compile.py:ro
There are also another changes in
docker-compose
directory, it were removed unused files, the docker_quickstart.py.example was rename to docker_quickstart.py to be the same patter like InstaPy (repo), the documentation has been updated with the changes, the DockerFile has been formatted to the Docker standards and also thesed
part has been updated to change the code without the necessity of using a line number.Basically with these changes the aim is to make the creation of the Docker InstaPy image transparent, using the latest version of InstaPy and reducing the pull requests in this repository; ie: #84