While tartufo started its life with one primary mode of operation, scanning the history of a git repository, it has grown other time to have a number of additional uses and modes of operation.
These are all invoked via different sub-commands of tartufo.
This is the “classic” use case for tartufo: Scanning the history of a git repository. There are two ways to invoke this functionality, depending if you are scanning a repository which you already have cloned locally, or one on a remote system.
$ tartufo scan-local-repo /path/to/my/repo To use docker, mount the local clone to the /git folder in the docker image:
$ docker run --rm -v "/path/to/my/repo:/git" godaddy/tartufo scan-local-repo /git $ tartufo scan-remote-repo https://github.com/godaddy/tartufo.git To use docker:
$ docker run --rm godaddy/tartufo scan-remote-repo https://github.com/godaddy/tartufo.git When used this way, tartufo will clone the repository to a temporary directory, scan the local clone, and then delete it.
When running any Git history scan, you can show scan progress by using the --progress or -p flag.
For more information click here.
The jobs command is a Bash builtin that lists all background and suspended processes belonging to the…
The Linux kernel writes messages to the kernel ring buffer throughout the boot process and…
rsync over SSH combines secure encrypted transport with fast incremental transfers. Instead of copying every file…
The pstree command in Linux displays running processes in a tree structure rather than a flat list.…
The type command in Linux shows how the current shell would interpret a name typed on the…
When a Linux system is slow or behaving unexpectedly, memory is one of the first…