|
1 | | -# dockerfile-pyinstalive |
2 | | -Dockerfile for PyInstalive. |
| 1 | +<!-- markdownlint-disable first-line-h1 --> |
| 2 | +[](https://hub.docker.com/r/mstmelody/image-name/builds) |
| 3 | +[](https://hub.docker.com/r/mstmelody/image-name/builds) |
| 4 | +[](https://hub.docker.com/r/mstmelody/image-name/dockerfile) |
| 5 | + |
| 6 | +# Quick reference |
| 7 | + |
| 8 | +- **PyInstaLive**: |
| 9 | + |
| 10 | + [dvingerh/PyInstaLive: Python script to download Instagram livestreams and replays.](https://github.com/dvingerh/PyInstaLive) |
| 11 | + |
| 12 | +<!-- markdownlint-disable no-trailing-punctuation --> |
| 13 | +# What is PyInstaLive? |
| 14 | +<!-- markdownlint-enable no-trailing-punctuation --> |
| 15 | + |
| 16 | +This Python script enables you to download any ongoing Instagram livestreams as well as any available replays. It is based on [another script](https://github.com/taengstagram/instagram-livestream-downloader) that has now been discontinued. |
| 17 | + |
| 18 | +# How to use this image |
| 19 | + |
| 20 | +1\. |
| 21 | +Create workspace directory to bind mount: |
| 22 | + |
| 23 | +```console |
| 24 | +mkdir workspace |
| 25 | +``` |
| 26 | + |
| 27 | +2\. |
| 28 | +Create [pyinstalive.ini](https://github.com/dvingerh/PyInstaLive#usage) into workspace directory: |
| 29 | + |
| 30 | +```text |
| 31 | +workspace |
| 32 | ++---pyinstalive.ini |
| 33 | +``` |
| 34 | + |
| 35 | +Note that setting `download_path` as `.` in `pyinstalive.ini` lets download livestreams into the workspace directory: |
| 36 | + |
| 37 | +```ini |
| 38 | +[pyinstalive] |
| 39 | +download_path = . |
| 40 | +``` |
| 41 | + |
| 42 | +3\. |
| 43 | +Download: |
| 44 | + |
| 45 | +```console |
| 46 | +docker run --rm --volume $(pwd)/workspace:/workspace mstmelody/pyinstalive <target username> |
| 47 | +``` |
| 48 | + |
| 49 | +However, if you press `Ctrl + C` to stop the container in the middle, the downloading file cannot be played. |
| 50 | + |
| 51 | +Therefore, first connect the terminal to the container to operate interactively: |
| 52 | + |
| 53 | +```console |
| 54 | +docker run -it --rm --volume $(pwd)/workspace:/workspace --entrypoint=bash mstmelody/pyinstalive |
| 55 | +``` |
| 56 | + |
| 57 | +Then download: |
| 58 | + |
| 59 | +```console |
| 60 | +pyinstalive -d <target username> |
| 61 | +``` |
| 62 | + |
| 63 | +In this case, the downloading process can be stopped with `Ctrl + C`, and the contents of the downloaded file can be played back up to that point. |
| 64 | + |
| 65 | +## ... via docker-compose |
| 66 | + |
| 67 | +It would be useful to create Compose file like: |
| 68 | + |
| 69 | +```yaml |
| 70 | +version: "3.8" |
| 71 | +services: |
| 72 | + pyinstalive: |
| 73 | + entrypoint: bash |
| 74 | + image: mstmelody/pyinstalive |
| 75 | + tty: yes |
| 76 | + volumes: |
| 77 | + - ./workspace:/workspace/ |
| 78 | +``` |
| 79 | +
|
| 80 | +You can connect the terminal to shell of the container by using following command to operate interactively: |
| 81 | +
|
| 82 | +```console |
| 83 | +docker-compose run --rm pyinstalive |
| 84 | +``` |
| 85 | + |
| 86 | +# License |
| 87 | + |
| 88 | +View license information for the software contained in this image. |
| 89 | + |
| 90 | +As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained). |
| 91 | + |
| 92 | +As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within. |
0 commit comments