Add a utility command for creating a new .env file about autoenv HOT 5 CLOSED

If this is accepted into the master, the Cookbook should be updated: the "Magic .env" section will become irrelevant, and best be replaced with a recommendation to put something like alias .env=autoenv_new in your .bash_aliases, etc.

from autoenv.

One possible problem with commit d676a0b is that it assumes that use_env has been defined. There are two ways that this could be made less confusing/assumptive to a user who hasn't looked at the wiki. (a) add a comment in the auto-generated .env file with the URL for the relevant Wiki; or (b) add the definition of use_env to the auto-generated .env file itself.

Solution B seems icky, so Solution A is implemented in commit 375d1c4.

from autoenv.

I don't really see the point of this when you can just run 'touch .env' ?

from autoenv.

Well, it's not just making an empty file. It creates a file with these contents:

# Assumes use_env. See https://github.com/kennethreitz/autoenv/wiki/Cookbook"
use_env $new_env_name

Where $new_env_name is the name of the present working directory. It's very simple, I thought that was the goal in using autoenv; simple ways to streamline switching projects and virtualenvs.

from autoenv.

I don't really see a point in this. Maybe it's just obsolete now.

from autoenv.