gotocode / envman Goto Github PK

There are currently no automatic hooks that run when some commits have been pushed to the envman repo.

In order to ensure that the code is correct, high-quality, and standards-compliant, we will need to add some kinds of hooks (e.g. Github Actions) to the repo.

We need to create a new command for listing out the named .env files created by envman.

Currently, the simplest way to do this is by running the following:

$ ls ~/envs

However, it's possible to make this more convenient by having a built-in command (e.g. list or ls) that displays this list for us.

As the title says, we need to add some usage examples to the main README.md to make it clearer as to the use-cases that envman is able to fulfill.

Currently, to view the contents of a previously saved .env file, we need to run the following commands:

$ envman load test.env
$ cat .env

By default, this will overwrite the .env file in the current directory, which is rather inconvenient.

We should add a new command (e.g. show or view) that allows the user to simply "print out" the contents of a saved .env file (without overwriting the file in the current directory).

As it stands, the main envman code for CLI interaction uses a bunch of if-elif-else statements to handle the various user commands.

It would be much cleaner (and more maintainable) if we used something like the click third-party library or argparse to handle command-line argument parsing and user interaction.

By default, envman uses a hard-coded directory to store the saved .env files (i.e. ~/envs).

We should allow the user to specify where envman should save these files (e.g. by using an environment variable like ENVMAN_ENVS_PATH).