Refresh the BloodHound quickstarts #1090
Conversation
| ``` | ||
|
|
||
| ``` bash Windows CMD | ||
| curl -L https://ghst.ly/getbhce > .\docker-compose.yml |
There was a problem hiding this comment.
? Can we change this to: curl -L https://ghst.ly/getbhce | docker compose -f - up
There was a problem hiding this comment.
The comment below for the same question applies here, but additionally, the piped command does not work consistently for Windows like this, hence the change.
|
|
||
| <CodeGroup> | ||
| ```bash Linux/MAC | ||
| curl -L https://ghst.ly/getbhce > .\docker-compose.yml |
There was a problem hiding this comment.
? Can we change this to: curl -L https://ghst.ly/getbhce | docker compose -f - up
There was a problem hiding this comment.
I would actually recommend we move this section to point towards using https://github.com/SpecterOps/bloodhound-cli instead.
We changed how the docs were structured away from the CURL one-liner because many of our users thought that they could use that instruction repeatedly and always maintain access to the latest version of BloodHound. Unfortunately, because of how Docker image library caching works, this would mean that customers would repeatedly use the same, originally downloaded version for later deployments. It also meant that customers who wanted to customize the deployments had a more complex time doing so.
As part of the Mintlify doc revamp, this PR:
Motivation and Context
This PR addresses: #1085
Testing
Tested locally with Mintlify for broken links and site rendering
Types of changes
I have read the CLA Document and I hereby sign the CLA