Related to my proposal on storage options #13, I think we are getting to the point where a full fledged CLI would be useful.
When designing, important to make sure we set sane defaults so it "just works" without arguments. This will help users unfamiliar with the tool get up and running quickly.
Brainstorming here but some arguments we may want to consider accepting via CLI this list is probably too large, whatever we do not support in CLI may be more appropriate for in a settings file:
- Stream tweets or search tweets
- Tweet limit used in stream or search
- Topics to stream/search
- Input file which contains list of topics
- Output type (file, ES, sqlite)
- File output location (S3, local file etc.)
- Location of credential file (Twitter, AWS)
Related to my proposal on storage options #13, I think we are getting to the point where a full fledged CLI would be useful.
When designing, important to make sure we set sane defaults so it "just works" without arguments. This will help users unfamiliar with the tool get up and running quickly.
Brainstorming here but some arguments we may want to consider accepting via CLI this list is probably too large, whatever we do not support in CLI may be more appropriate for in a settings file: