Skip to content

Building 70 Projects ranging from beginner to advanced so anyone can β€” learn from, build upon, use as a reference, or even copy directly. Owned by my cybersecurity company πŸ‘‡

Update README with Go install instructions

Carter Perezefc05206f70e
diff --git a/PROJECTS/docker-security-audit/README.md b/PROJECTS/docker-security-audit/README.md
index c1b10ad6..10f2c847 100644
--- a/PROJECTS/docker-security-audit/README.md
+++ b/PROJECTS/docker-security-audit/README.md
@@ -38,14 +38,14 @@ go build -o docksec ./cmd/docksec
This builds a binary in the current directory. The `./` is required because the binary is not in your PATH.
-### Option 2: Go install (for Go developers)
+### Option 2: Go install (for Go developers) This same project lives in a seperate repo https://github.com/CarterPerez-dev/docksec - in order to be able to:
```bash
go install github.com/CarterPerez-dev/docksec/cmd/docksec@latest
docksec scan
```
-This downloads the source, compiles it on your machine, and puts the binary in `~/go/bin/`. If that directory is in your PATH, you can run `docksec` directly without `./`.
+Because downloads the source, compiles it on your machine, and puts the binary in `~/go/bin/`. If that directory is in your PATH, you can run `docksec` directly without `./`.
The `/cmd/docksec` path is needed because the main package lives in that subdirectory, not at the repo root.