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

Add ability to read devenv.yml from URL #116

Open
LeslieGerman opened this issue Sep 10, 2020 · 3 comments
Open

Add ability to read devenv.yml from URL #116

LeslieGerman opened this issue Sep 10, 2020 · 3 comments

Comments

@LeslieGerman
Copy link

Hi Devs,

I would like to suggest a new feature for your great tool!

Conda latest version allows using URL for the environment yaml file:

conda env create -f https://domain.com/my-environment.yml

See conda/conda#9835

Having this ability in conda-devenv would be good, as well.
Regards

@prusse-martin
Copy link
Member

I agree on that.

How will it deal with "include"s?
Should it define a variable similar to how is_included is added to the jinja template namespace and let the author conditionally define "url and no url based includes"?

@nicoddemus
Copy link
Member

How will it deal with "include"s?

Good question.

I think it is sufficient to distinguish between local and URLs automatically? For example pip let me do this:

pip install package.tar.gz
pip install https://someserver.com/package.tar.gz

I suppose include could work in the same way?

@LeslieGerman
Copy link
Author

let the author conditionally define "url and no url based includes"?

Good point, but right now I don't see a reason to distinguish that.

I think it is sufficient to distinguish between local and URLs automatically?

I think it's enough.

Allowing URLs in "include" fosters code-reuse (in our case yaml reuse 😄 ), and helps organizing the work of geographically distributed team. E.g. a common devenv.yml, which is located on some central website, can be included in the yaml of various remote developers. Thus, any improvement on the central yaml are "automatically" applied on the work of the distributed team.
If they have fast internet connection... 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants