Closed fridex closed 3 years ago
Worth to have a look at https://pypi.org/project/private-pypi/
Another candidate: https://www.devpi.net/
/livecycle active
See https://github.com/thoth-station/httpd-aicoe-container/issues/28#issue-649136008 for checking correctness of the index.
Closing, Pulp deployment is WIP which will be used as a package index: https://github.com/operate-first/support/issues/176
/close
@fridex: Closing this issue.
Is your feature request related to a problem? Please describe.
Currently, we run an HTTP server that serves a static content from within the directory. To help to scale and maintaining multiple python packages, we could have a look for an alternative. The HTTP server needs to be rebuilt each time a package is about to be added which does not integrate very well.
Describe the solution you'd like
Deploy one or multiple pypiserver instances to serve python packages. As pypiserver can serve python packages, we would gain possiblity to upload built artifacts directly from AICoE-CI. A use case for this could be integration of https://github.com/thoth-station/thoth-application/issues/955 when we would build numpy and publish it on our index using AICoE-CI pipeline.
See relevant issue on pypiserver: https://github.com/pypiserver/pypiserver/issues/382
A downside of this solution is authentication exposure to the world.
Describe alternatives you've considered
Keep serving Python packages using the index stated.
Additional context
We could also start being package agnostic. The current url to our AICoE index is specific to "tensorflow". This can be misleading if we build or host our own python artifacts.
https://tensorflow.pypi.thoth-station.ninja/