Command line interface for testing internet bandwidth using speedtest.net servers.
1.0K
This is a repository with various applications written in Python and installed in Docker.
bpytop - bpytop: Resource monitor that shows usage and stats for processor, memory, disks, network and processes. GitHubcatt - Cast All The Things: Allows you to send local/online videos or webpages to your Chromecast. GitHubicdiff - Improved colored diff. GitHubjc - JSONifies the output of many CLI tools and file-types for easier parsing in scripts. GitHubspeedtest-cli - Command line interface for testing internet bandwidth using speedtest.net servers. GitHubstig - TUI and CLI for the BitTorrent client Transmission. GitHubtremc - Console client for the BitTorrent client Transmission. GitHubwe-get - Command-line tool for searching torrents. GitHubBelow are various examples for the above applications. I will try to keep this list updated as more items are added.
The following example runs bpytop with the host processes (using --pid=host) and network activity information (using --net=host) passed to the Docker image, as well as setting a volume for holding the bpytop configuration between executions (using -v bpytop:/root/.config/bpytop/).
docker run --rm -it \
--pid=host \
--net=host \
-v bpytop:/root/.config/bpytop/ \
macgyverbass/bpytop
Note that /root/.config/bpytop/ is optional, but will lose any custom settings made within the program. You can also set a bind mount to a host folder for keeping the configuration persistent.
The following example runs catt with the command argument scan on the host network. You can also use a macvlan for this, as long as it is on the same network as your Chromecast devices.
docker run --rm -it \
--network=host \
macgyverbass/catt \
scan
The following example runs icdiff with the current path bind-mounted (as read-only in this example) and with the files before.txt and after.txt being compared.
docker run --rm -it \
-v "${PWD}":"${PWD}":ro -w "${PWD}" \
macgyverbass/icdiff \
"before.txt" "after.txt"
The following example pipes the output of ls -l into jc with the argument --ls and it will return JSON text, which then can be piped into jq or another application needing JSON input. Note that in this example, the -i arugment for docker run is omitted, as -i will prevent the Docker entrypoint from receiving the piped data.
ls -l | docker run --rm -t \
macgyverbass/jc \
--ls
The following example runs speedtest-cli using the --secure argument. Note that speedtest-cli also runs without any arguments passed to it.
docker run --rm -it \
macgyverbass/speedtest-cli \
--secure
The following example runs stig on the host 192.168.0.80 on port 9095. Note that your IP/port will depend on your Transmission server setup. Remember to review the documentation on the official website for more details using this executable.
docker run --rm -it \
macgyverbass/stig \
set connect.host 192.168.1.0 \; set connect.port 9091 \;
The following example runs tremc on the host 192.168.0.80 on port 9095. Note that your IP/port will depend on your Transmission server setup. Remember to review the documentation on the official website for more details using this executable.
docker run --rm -it \
macgyverbass/tremc \
--connect 192.168.0.80:9095
The followinig example runs we-get with the search term "linux" and with the output in JSON using the -J switch.
docker run --rm -it \
macgyverbass/we-get \
--search "linux" -J
Your uses will differ from the above examples, but they can be used as a guide for running them on your system.
Content type
Image
Digest
Size
16.5 MB
Last updated
about 5 years ago
docker pull macgyverbass/speedtest-cli