Save output to path

[cgeopapa]

Changed the behavior of -o and -s options. They now receive a path as an argument for the path to save the resulting file. JSON file is now updated with every new Google search. README.md is also updated to reflect these changes.

Example usage: python pagodo.py -g dorks/all_google_dorks.txt -s ~/pagodo/results.txt -o ~/some_folder/pagodo_results.json

[opsdisk]

Thanks for submitting a PR @cgeopapa - give me a few days to take a look at it.

[opsdisk]

Hey @cgeopapa I just pushed some updates to the PR. I might have a few smaller tweaks, but it's mostly done.

• I like your idea of being able to specify a path to save the files, but want to maintain the backwards functionality of auto-generating a file name if one isn't provided. If one is provided, like in your original examples, it will honor that.
• When you moved the json file writer inside the loop, it won't save the completion_timestamp because the file will be saved before it's generated. If you have a really strong case for being able to monitor real time updates to a json file vs the text file, I can re-consider.
• I want to still track the dorks/ directory so I removed that from .gitignore

Take it for a spin and let me know what you think.

[opsdisk]

You ever get a chance to test the code @cgeopapa ?

[opsdisk]

Thank you for the PR @cgeopapa!