chulderman/stellar-avarice

stellar-avarice's Issues

implement libtorrent

worth implementing - or just output to a watch directory and use known client?

Compare Versions

1. Compare files with previous versions.

2. If hash hasn't changed, pull the file forward

   Create a hard link.
   (Doable on windows?)

3. Skip downloading file

---

Optional: Display verbose list of what files have changed.

Documentation

Improve documentation

Local peer-to-peer implementation

(Project independent)
Implement a server to create a torrent of the whole build so that users can seed to each other locally.

(Project Dependent)
Optionally grab the torrent file of the build and allow the user to download the build via peer-to-peer.

Add CLI handling

Options:

• HTTP vs Torrent download
• Create torrent
• Check for new release
• Print info (latest release, up-to-date?)
• more?

Don't download files we already have

Issue Title.

Change output to progress bar for build checking

Printing out what we're trying is stupid. Let's make it pretty.

urllib2 runs out of memory while downloading

Known issue. Should be resolved by resolving issue #4

Stream latest json data and just store the current build # locally

As per issue title, instead of saving the json locally, we can simply test for the file and store the latest file. The json processing will then stream the content when it parses. No need to download it.

Convert urllib2 to requests