AFAICS this should be pretty straightforward to implement, if we can agree on the following criteria for the content provider:
the URL contains .zip (or even ends with that)
a HEAD request returns content that could be a ZIP file (might not work on some/many servers), i.e. Content-Type: application/zip, Content-Encoding: gzip
Proposed change
Add support for downloading ZIP files instead of a repo:
repo2docker https://example.com/an-archive.zip
This comes straight from the repo2docker roadmap, admittedly in the "later" section, but IMO this could be a good first issue for new contributors.
AFAICS this should be pretty straightforward to implement, if we can agree on the following criteria for the content provider:
.zip
(or even ends with that)HEAD
request returns content that could be a ZIP file (might not work on some/many servers), i.e.Content-Type: application/zip
,Content-Encoding: gzip
Here's a little experiment for the headers:
Related issue: #795
Alternative options
Don't support it.
Who would use this feature?
People who want to test run (maybe privately) a repository, and users of not supported websites and repositories.
How much effort will adding it take?
Half a day.
Who can do this work?
Developer with basic Python skills, if helped with the repo2docker code base.