AstraLuma / xontrib-avox

autovox policy based on project directories
GNU General Public License v3.0
10 stars 3 forks source link

How avox define which env must be used? #4

Closed worldmind closed 6 years ago

worldmind commented 6 years ago

I am sorry, but I can't understood from readme how avox define which env must be used in concrete dir? For example, I create virtualenv named django11 via vox, create project directory djtest. How say to avox that after cd to djtest is must activate django11 env?

AstraLuma commented 6 years ago

avox uses vox-managed virtual environments, where the project directory name matches the venv name.

For example, if you've set $PROJECT_DIRS = ["~/code"] and have the project directory ~/code/spam, avox will use the venv name spam.

This is the only policy that will ever be supported by avox, by design. If this is not suitable for you, I heartily support blatently copying the code and making your own project with your own ideas of how projects should map to environments.

worldmind commented 6 years ago

@astronouth7303 thanks for explanation, I think this phrase:

For example, if you've set $PROJECT_DIRS = ["~/code"] and have the project directory ~/code/spam, avox will use the venv name spam.

needed to be in README