Skip to content
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 remote environment definitions #127

Open
AlbertDeFusco opened this issue Jul 13, 2023 · 0 comments
Open

Support remote environment definitions #127

AlbertDeFusco opened this issue Jul 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@AlbertDeFusco
Copy link
Contributor

It would great to enable remote sources for environments

name: my-project

environments:
  not-locked-env:
    - <protocol>://<path>/<to>/<environment-yaml>[?param1=value&param2=value]
  pre-locked-env:
    - <protocol>://<path>/<to>/<conda-lock-yaml>[?param1=value&param2=value] 

In the first env not-locked-env the remote definition is the intentional spec and the lockfile will be computed and stored locally.

In the second environment the remote definition is to the lockfile. Here we would not need to run conda-lock locally or store the file locally.

@AlbertDeFusco AlbertDeFusco added the enhancement New feature or request label Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant