You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can install a package from a private repo at a specific git commit as documented using my personal access token.
However, when a teammate then tries to spin up my project with uv sync, it just hangs as previously reported here. This makes sense, as the uv.lock does not (and should not) include my access token.
Although you've clarified that you don't support interactive authentication, might there already be a way for a user to configure environment variables so that uv sync would just work?
Short of that, my current workaround for someone else to set up a venv consistent with mine is kinda ugly:
uv venv
# for each private repo do
uv add git+https://${TOKEN_VARIABLE}...
# now that ^^ are already installed, we can pick up all the other deps specified in `uv.lock`:
uv sync
The text was updated successfully, but these errors were encountered:
zkurtz
changed the title
sync with authentication
sync with token-based authentication
Dec 19, 2024
I can install a package from a private repo at a specific git commit as documented using my personal access token.
However, when a teammate then tries to spin up my project with
uv sync
, it just hangs as previously reported here. This makes sense, as theuv.lock
does not (and should not) include my access token.Although you've clarified that you don't support interactive authentication, might there already be a way for a user to configure environment variables so that
uv sync
would just work?Short of that, my current workaround for someone else to set up a venv consistent with mine is kinda ugly:
The text was updated successfully, but these errors were encountered: