Your ROOT_URL in app.ini is https://git.cloudchain.link/ but you are visiting https://dash.bss.nz/open-source-mirrors/sherlock/commit/1dd1b45802181e534478da3749a1fdafdb6f03d7?style=split&whitespace=show-all
You should set ROOT_URL correctly, otherwise the web may not work correctly.
<span>Hunt down social media accounts by username across <ahref="https://github.com/sherlock-project/sherlock/blob/master/sites.md">social networks</a></span>
<span>Hunt down social media accounts by username across <ahref="https://github.com/sherlock-project/sherlock/blob/master/sites.md">social networks</a></span>
<atarget="_blank"href="https://twitter.com/intent/tweet?text=%F0%9F%94%8E%20Find%20usernames%20across%20social%20networks%20&url=https://github.com/sherlock-project/sherlock&hashtags=hacking,%20osint,%20bugbounty,%20reconnaissance"title="Share on Twitter"><imgsrc="https://img.shields.io/twitter/url/http/shields.io.svg?style=social"></a>
@ -107,7 +99,7 @@ Accounts found will be stored in an individual text file with the corresponding
## Anaconda (Windows) Notes
## Anaconda (Windows) Notes
If you are using Anaconda in Windows, using 'python3' might not work. Use 'python' instead.
If you are using Anaconda in Windows, using `python3` might not work. Use `python` instead.
## Docker Notes
## Docker Notes
@ -123,26 +115,14 @@ Once the image is built, sherlock can be invoked by running the following:
docker run --rm -t mysherlock-image user123
docker run --rm -t mysherlock-image user123
```
```
The optional ```--rm``` flag removes the container filesystem on completion to prevent cruft build-up. See: https://docs.docker.com/engine/reference/run/#clean-up---rm
The optional ```-t``` flag allocates a pseudo-TTY which allows colored output. See: https://docs.docker.com/engine/reference/run/#foreground
Use the following command to access the saved results:
Use the following command to access the saved results:
```
```
docker run --rm -t -v "$PWD/results:/opt/sherlock/results" mysherlock-image -o /opt/sherlock/results/text.txt user123
docker run --rm -t -v "$PWD/results:/opt/sherlock/results" mysherlock-image -o /opt/sherlock/results/text.txt user123
```
```
<!-- The ```-v "$PWD/results:/opt/sherlock/results"``` options tell docker to create (or use) the folder `results` in the
present working directory and to mount it at `/opt/sherlock/results` on the docker container.
The `-o /opt/sherlock/results/text.txt` option tells `sherlock` to output the result. -->
Docker is instructed to create (or use) the folder `results` in the current working directory and to mount it at `/opt/sherlock/results` on the docker container by using the ```-v "$PWD/results:/opt/sherlock/results"``` options. `Sherlock` is instructed to export the result using the `-o /opt/sherlock/results/text.txt` option.
Docker is instructed to create (or use) the folder `results` in the current working directory and to mount it at `/opt/sherlock/results` on the docker container by using the ```-v "$PWD/results:/opt/sherlock/results"``` options. `Sherlock` is instructed to export the result using the `-o /opt/sherlock/results/text.txt` option.
Or you can use "Docker Hub" to run `sherlock`:
```
docker run theyahya/sherlock user123
```
### Using `docker-compose`
### Using `docker-compose`
@ -175,7 +155,7 @@ The following is an example of the command line to run all the tests for
Sherlock. This invocation hides the progress text that Sherlock normally
Sherlock. This invocation hides the progress text that Sherlock normally
outputs, and instead shows the verbose output of the tests.
outputs, and instead shows the verbose output of the tests.