./ghostwriter-cli install doesn't work as it always shows "-bash: ./ghostwriter-cli: No such file or directory" on Windoes Laptop/Ubantu

GhostManager / Ghostwriter

The SpecterOps project management and reporting engine

https://ghostwriter.wiki

BSD 3-Clause "New" or "Revised" License

1.23k stars 174 forks source link

./ghostwriter-cli install doesn't work as it always shows "-bash: ./ghostwriter-cli: No such file or directory" on Windoes Laptop/Ubantu #391

Closed island7 closed 1 week ago

island7 commented 4 months ago

Describe the bug ./ghostwriter-cli install doesn't work as it always shows "-bash: ./ghostwriter-cli: No such file or directory" on Windoes Laptop/Ubantu

To Reproduce Steps to reproduce the behavior:

Go to 'Ubantu'
Command ./ghostwriter-cli install doesn't work as it always shows "-bash: ./ghostwriter-cli: No such file or directory" on Windoes Laptop/Ubantu

Expected Behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Server Specs:

OS: [e.g., Ubuntu]
Docker [e.g., output of docker --version and docker-compose -v]
Ghostwriter [e.g., 2.2.3 or whatever is printed at the bottom of the left-hand sidebar]

Additional context Add any other context about the problem here.

chrismaddalena commented 4 months ago

Hey @island7, check to make sure you are in the Ghostwriter directory with ghostwriter-cli.exe. If you cloned Ghostwriter into a directory named Ubantu, you'll need to cd into .../Ubantu/Ghostwriter to be in the correct directory with the CLI binaries and necessary files for the install.

unixerius commented 1 month ago

@chrismaddalena, @island7 was making typos. They did not clone the GhostWriter repo into a directory called "Ubantu", they mean they are trying to install and run GhostWriter in Ubuntu Linux, under Windows. I suspect they are using WSL2.

This also means that @island7 should be using ghostwriter-cli-linux and not ghostwriter-cli (despite what the quickstart in the wiki says).

Please go ahead and close this issue.

github-actions[bot] commented 3 weeks ago

This issue has been labeled as stale because it has been open for 30 days with no activity.

github-actions[bot] commented 1 week ago

This issue is closed because it has been inactive for 14 days since being labeled stale. Feel free to re-open the issue with a comment. If this needs further discussion (e.g., a feature request), it might be better to open a topic under the Discussions tab.