-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support devpi inside docker containers #3553
Labels
Milestone
Comments
This was cloed automatically but @agjohnson said my implementation in the PR is not a replacement of this issue. So, I'm reopening it. |
agjohnson
added
Accepted
Accepted issue on our roadmap
and removed
Accepted
Accepted issue on our roadmap
labels
Jun 8, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
stsewd
added
Accepted
Accepted issue on our roadmap
and removed
Status: stale
Issue will be considered inactive soon
labels
Jan 10, 2019
humitos
added a commit
that referenced
this issue
Oct 30, 2019
Adds a new service for docker-compose that spin up a devpi-server to cache all the Python packages used by the builders. If configured, `--index-url` and `--trusted-host` is added to all the `pip` commands. Fixes #3553
humitos
added a commit
that referenced
this issue
Oct 30, 2019
Adds a new service for docker-compose that spin up a devpi-server to cache all the Python packages used by the builders. If configured, `--index-url` and `--trusted-host` is added to all the `pip` commands. Fixes #3553
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Devpi[1] is a great tool to help with intermittent connections. While I am traveling (airports/airplanes/spotty cell service), I find myself wanting a local pypi server. Devpi allows for online and offline usage, and so normal day to day usage on solid internet connections should seed a cache that can be used offline.
The problem blocked this from use is that the docker container would need to be created with additional options, forwarding the host (or another docker container hosting devpi). One option around this might be to create a signal that can be caught before running the docker command to create the container, and allow for alteration of the dictionary that we pass to the docker API. This would allow for a custom RTD plugin that would add a link to a devpi container, or an additional forwarded port/etc.
The text was updated successfully, but these errors were encountered: