mirror
/
repo2docker
kopia lustrzana https://github.com/jupyterhub/repo2docker
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność
2 109 Commity
6 Gałęzie
21 Tagi
6,6 MiB
Wykres commitów

44 Commity (e7e4dd9ee31fe870542f742df995b18405e9ec7a)

Autor SHA1 Wiadomość Data
Simon Li 787d1d3aeb Container engine is an entrypoint: repo2docker.engines 2021-07-02 12:43:15 +01:00
Simon Li 23c1be9d1c setup.py: install_requires in alphabetical order 2021-02-19 19:25:12 +00:00
Simon Li f24cbef5f1 setup.py: Remove duplicate requests from install_requires 2021-02-19 19:25:04 +00:00
David Douard e54c24ce2e Add support for the SWHID content provider 
This content provider allows to retrieve the content from a
Software Heritage (SWH) persistent identifier (SWHID).
Typical usage:

  repo2docker swh:1:rev:94dca98c006b80309704c717b5d83dff3c1fa3a0

It uses the SWH public vault API to retrieve the content of the given
directory.

Most of the times, this will not need an authentication
token to bypass the rate-limiting of the SWH API.
Without authentication, one should be allowed to retrieve one
directory content per minute.

If this is not enought, then the user must use authenticated calls to
the SWH API.

For this, a new `swh_token` config item has been added to the Repo2Docker
application class.

To use authentication:

  repo2docker --config cfg.json swh:1:rev:94dca98c006b80309704c717b5d83dff3c1fa3a0

with the swh_token config option being defined in the cfg.json config file.
 2021-01-19 18:04:46 +01:00
David Douard 830a9c89c0 Replace urllib by requests in contentproviders 
requests is globally simpler to use, and more and more people
are more familiar with this later than urllib.
 2021-01-18 17:29:53 +01:00
Tim Head ad80defc12 Bump Python requirement to 3.6 from 3.5 
This increases the lowest version of Python required to run repo2docker itself.
 2020-09-07 08:02:09 +02:00
Min RK 60555b1d05 update repo URLs for jupyterhub/repo2docker 2020-08-10 09:33:05 +02:00
Daniel Nüst 3bdf7041dc sort and pretty print dataverse.json 
so that we can track changes and only update the lines of the files that need updating
 2019-09-18 08:54:48 +02:00
Kacper Kowalik (Xarthisius) 063fd4dd9a
Add a command for generating dataverse data file 2019-09-13 13:42:41 -05:00
Tim Head 8b004e06dc Apply auto formatting 
Apologies to anyone finding this commit via git blame or log

run the autoformatting by

    pre-commit run --all-files
 2019-06-03 21:37:25 +02:00
Tim Head 5303010d0e Drop support for Python 3.4 2019-05-21 22:10:55 +02:00
David Anthoff f3d0bf41e3 Add semver detection logic 2019-02-27 22:05:23 -08:00
David Anthoff 26eecc7548 Start reading julia version from Project.toml 2019-02-25 22:38:56 -08:00
Nokome Bentley b40558f448 Better approach to dealing with alt Python versions 
As suggested by @betatim https://github.com/jupyter/repo2docker/pull/472#issuecomment-439219985
 2018-11-16 12:08:45 +13:00
Nokome Bentley 6d496eee91 Ensure Python3 before reading README with encoding arg 
If you accidently try to install using Python 2 you get the error

    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/home/nokome/nokome/repo2docker/setup.py", line 5, in <module>
        with open('README.md', encoding="utf8") as f:
    TypeError: 'encoding' is an invalid keyword argument for this function

Ideally the user would be aked to use Python 3 as `python_requires` tells us,
but which isn't reached yet.
This implements that behaviour.
 2018-11-16 11:37:30 +13:00
Tim Head af669d6202 Modify short project description 2018-09-09 17:20:52 +02:00
Tim Head 7ca12eec6c Add keywords to setup() metadata 2018-09-09 09:13:06 +02:00
Tim Head f725426344 Add more details to our setup command 2018-09-09 07:50:37 +02:00
Tim Head 60ebcfe2bd Add versioneer support 2018-07-02 22:03:53 +02:00
Tim Head 1967ca4903 Bring the versions in sync 2018-07-02 21:50:06 +02:00
yuvipanda eca6f7159f Use v0.5.0 than v0.5 to be consistent 2018-02-07 11:37:37 -08:00
yuvipanda 7d2e8ccaeb Bump version to v0.5 2018-02-07 11:33:39 -08:00
Min RK 47ab8bb55f add ruamel.yaml dependency for parsing environment.yml 2018-01-03 18:20:41 +01:00
yuvipanda 0ff424ca7e Add 'repo2docker' as a script alias 
jupyter-repo2docker is a mouthful
 2017-10-24 16:09:40 -07:00
yuvipanda d97eee9a6a Bump version number 2017-09-06 12:47:23 -07:00
yuvipanda dbf4d16a61 Remove unneeded print function import 
We only support 3.4
 2017-08-14 12:00:54 -07:00
yuvipanda c2a5a84652 Bump version number 2017-08-14 11:42:13 -07:00
yuvipanda bef5f1f969 Include package_data in setup.py 
This was causing all conda based builds to fail
 2017-08-11 17:15:35 -07:00
yuvipanda 8f42312fc2 Mark repo2docker as requiring at least Python 3.4 
And test with 3.4 on Travis.
 2017-07-30 02:08:48 -07:00
yuvipanda b860bc3359 Get rid of s2i packaging code from setup.py 
We no longer use s2i, so no need to do all the wheel
business!
 2017-07-28 19:35:17 -07:00
yuvipanda ed059188f3 Add jinja2 as a dependency 2017-07-28 19:35:17 -07:00
yuvipanda a8ac7f26ff Commit Julia's s2i assemble files! 
They were accidentally ignored by the .gitignore!
 2017-07-01 01:11:52 -07:00
yuvipanda 7146ae3c52 Bump julia builder version to match new 0.6 Julia 2017-06-30 23:37:34 -07:00
yuvipanda 88da963a67 Tag new version 2017-06-30 23:22:53 -07:00
yuvipanda 12c0be20fd Bump version number 2017-06-03 17:48:09 -07:00
yuvipanda 2a092c974d Bump version number 2017-05-30 22:43:33 -07:00
Min RK e7674ce96c bump version to 0.2.0 2017-05-24 17:17:57 -07:00
Min RK 683a94fb80 apply platform tag to wheels 2017-05-24 10:01:24 -07:00
Min RK bba7582886 bundle s2i binary 
only for linux, darwin for now. Still need to apply tag to wheels.
 2017-05-24 09:48:53 -07:00
yuvipanda eac759ccd4 Add explicit dependency on escapism 2017-05-22 22:55:44 -07:00
yuvipanda e3224392e0 Add a __main__ and an entrypoint 2017-05-22 20:39:12 -07:00
yuvipanda 93972e9b58 Rename builder to repo2docker 
Package name is jupyter-repo2docker
 2017-05-22 16:22:36 -07:00
yuvipanda 91e41fca90 Revamp logging to provide structured JSON logs 
- Filter out useless info from docker build / push steps
- Use JSON logging everywhere. User readable messages go into
  message, extra useful info goes into extra.
- Capture output from all spawned processes and stuff them
  into an appropriate JSON structure
 2017-05-15 18:54:51 -07:00
yuvipanda 0399583ba8 Add setup.py 2017-05-09 01:46:26 -07:00