repo2docker/repo2docker/contentproviders/__init__.py

from .base import Local
from .dataverse import Dataverse
from .figshare import Figshare
from .git import Git
from .hydroshare import Hydroshare
from .mercurial import Mercurial
from .swhid import Swhid
from .zenodo import Zenodo
Start using content providers 2018-02-18 12:41:22 +00:00			`from .base import Local`
Add Dataverse content provider 2019-07-10 22:44:03 +00:00			`from .dataverse import Dataverse`
[pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci 2022-10-31 22:32:14 +00:00			`from .figshare import Figshare`
			`from .git import Git`
initial checkin of hydroshare content provider 2019-08-22 22:30:48 +00:00			`from .hydroshare import Hydroshare`
Add a Mercurial contentprovider MyBinder could support Mercurial repositories See https://github.com/jupyterhub/binderhub/issues/1148 2020-09-04 13:14:04 +00:00			`from .mercurial import Mercurial`
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. 2020-11-24 17:30:08 +00:00			`from .swhid import Swhid`
[pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci 2022-10-31 22:32:14 +00:00			`from .zenodo import Zenodo`