Investigate approaches for packaging project

[chrisbillows]

Explore alternative approaches for a new user to install, configure and run the application.

It could follow this shape:

Version One 1) User clones repo from GitHub 2) User installs the application to make command line access native e.g. rts --help - should this be via pip, pipx or both? 3) The User is instructed in the GitHub README.md to run configuration e.g rts configure.

• The configure step asks the user for their Raindrop.io and Todoist API keys. 4) The User can optionally install background running via a second "install" step with rts install plist (with an equivalent rts uninstall plist)
  • This will then install the automation file (and uninstall)
  • It should include an optional argument for duration
  • Can we automate loading the plist file or semi-automate with user approval? 5) The User can optionally run the application in an interactive terminal via rts run
• This should include optional arguments for interval and total number of runs
• This should include a warning that the terminal needs to be kept open

Version Two 1) Replace manually cloning the repo with installing via PyPi.

Version Three 1) Create an installable .pkg

• a .pkg will likely be required due to requiring User permissions during installation
• could this kind of installer include activating the required Raindrop.io in a more user understandable way?

Necessary steps to consider:

• [ ] Where should things be installed on a users machine (app code, database, plist)
• [ ] Bash vs. python for creating/installing the plist file
• [ ] Can both pip and pipx installation be offered? Confusing?
• [ ] What do we need for PyPi?
• [ ] Can we structure Version One in a way that will easily fits the requirements of Version Two?
• [ ] Ditto can we Version one in a way that will easily fit the requirements of Version Three?