Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Sherlock Run Wherever As a Shell Tool/Script? #1740

Open
1 of 2 tasks
DroWnThePoor opened this issue Mar 13, 2023 · 3 comments
Open
1 of 2 tasks

Make Sherlock Run Wherever As a Shell Tool/Script? #1740

DroWnThePoor opened this issue Mar 13, 2023 · 3 comments
Labels
question Further information is requested

Comments

@DroWnThePoor
Copy link

Checklist

  • I'm asking a question regarding Sherlock
  • My question is not a tech support question.

We are not your tech support.
If you have questions related to pip, git, or something that is not related to Sherlock, please ask them on Stack Overflow or r/learnpython

Question

ASK YOUR QUESTION HERE

Is there a way to go about using Sherlock outside of the directory it's installed in?
Forgive if this is something obvious. If it is, just a keyword that I can search on how to do so would be appreciated.
I noticed someone mentioned the MAIN_ issue and the answer was that it needed to happen in the directory.

@DroWnThePoor DroWnThePoor added the question Further information is requested label Mar 13, 2023
@amirrossein
Copy link

@DroWnThePoor if you didn't use a virtualenv to install dependencies, you can add an alias to your bash profile, something like this:

alias sher="python3 [path to the sherlock root]/sherlock/sherlock"

@DroWnThePoor
Copy link
Author

Thank you I can give this a try, but I'm not sure if I used virtuallenv or not as I cloned/built Sherlock a couple years ago, originally.
I'm pretty sure I did us Pip for dependencies at some point, but virtualenv is something you set manually for isolating dependencies to a specific build tree?
I'm not a real dev so I'm guessing based on a cursory search of the term.

@DeFidelity
Copy link

If you just use pip to install without doing anything like python -m venv ... then you most probably didn't use a venv for your installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants