Skip to content
Elizabeth Williams edited this page Feb 18, 2015 · 1 revision

Possible Workflow

  1. "bot sync_mal":
  • Pulls in MAL's wanting to watch or watching status of the user specificed in config
  • Pulls in information for each series (Number of episodes, alternate titles maybe?)
  • Creates a download request for each episode
  1. "bot download"
  • First attempts to resume any interrupted downloads
  • Goes through each download request and downloads the file.
  • On each connection close (download done or interrupted) marks each request as finished or interrupted
  1. ???, do you need to resync to MAL or anything?
  2. Profit.

Storage

Right now I use a comma separated text file (botname,packnum,filename) to download each file, if we want to track what's already been downloaded then we should probably move to something better. Like SQLite. This has a lot of advtanges like actually linking each downloaded episode to its series and lots of room to make a web interface to the same database to help us do stuff if we want.

Use

I'm not sure how a person actually uses this, maybe they just run commands("bot sync_mal", "bot download", "bot remove series"). If they wanted it to happen daily/nightly/perodically they could set their own chron job.

How everything works together

"bot sync_mal" ----------------------------> writes to SQLite DB (file_generator.py + fetch_packlists.py)

"bot download" <-------------------------> reads from and writes to SQLlite (download_bot.py)

bot sync_mal updates/fills in the series table and creates download requests for each episode

Clone this wiki locally