Alternative install methods

Python package
1. Build from source
Docker Container

Python

# pipx is recommended, but pip may suffice if pipx is unavailable
pipx install sherlock-project

Build live package from source (useful for contributors)

Building an editable (or live) package links the entry point to your current directory, rather than to the standard install location. This is often useful when working with the code base, as changes are reflected immediately without reinstallation.

# Assumes repository cloned, and pwd is repository root
pipx install -e .

Run package from source (no install)

If you'd rather not install directly to your system, you can import the module at runtime with -m.

# Assumes repository cloned, and pwd is repository root
python3 -m sherlock user123 user789

Docker

Note

Sherlock doesn't yet have context detection. It's recommended that Docker containers be ran with option -o /opt/sherlock/results/{user123}.txt (replace {user123}) when an output file is desired at the mounted volume (as seen in the compose).

This has no effect on stdout, which functions as expected out of the box.

# One-off searches
docker run --rm -t sherlock/sherlock user123

# If you need to save the output file... (modify as needed)
# Output file will land in ${pwd}/results
docker run --rm -t -v "$PWD/results:/opt/sherlock/results" sherlock/sherlock -o /opt/sherlock/results/text.txt user123

# At any time, you may update the image via this command
docker pull sherlock/sherlock

Using compose

version: "3"
services:
  sherlock:
    container_name: sherlock
    image: sherlock/sherlock
    volumes:
      - ./sherlock/:/opt/sherlock/results/

docker compose run sherlock user123

Build image from source (useful for contributors)

# Assumes ${pwd} is repository root
docker build -t sherlock .
docker run --rm -t sherlock user123

3.4 KiB Raw Blame History