Drop dotenv module requirement

Author: pjeby

README.md

@@ -30,7 +30,6 @@ Dependencies are installed to a `.deps` directory, with executables in `.deps/bi
 - [.devkit Modules](#devkit-modules)
 - [All-Purpose Modules](#all-purpose-modules)
   * [cram](#cram)
-  * [dotenv](#dotenv)
   * [shell-console](#shell-console)
 - [Watch Modules](#watch-modules)
   * [entr-watch](#entr-watch)
@@ -150,14 +149,6 @@ As long as you run cram via `script/test`, `dk test`, or `dk cram`, you can plac
 
 Setup files can source other shell files, including other directories' `cram-setup.sh` files if you need to share setup between directories (e.g. `source "$TESTDIR/../cram-setup.sh"` to source and extend a parent directory's setup).  You can also just symlink from one cram-setup.sh to another.
 
-#### dotenv
-
-The [dotenv](modules/dotenv) module sources a local clone of the [bashup/dotenv](https://github.com/bashup/dotenv/) tool for manipulating .env files in [docker-compose format](https://docs.docker.com/compose/compose-file/#env_file).  After a `dk use: dotenv`, the rest of your `.dkrc` can use the `.env` function to read, edit, and set defaults in `.env` files -- perfect for project setup scripts or other commands that need configuration.
-
-In addition, if you are using `direnv` (or the console command of the shell-console module), then you can also use the `dotenv` command directly on the command line.
-
-For more information on how `dotenv` and `.env` work, please see the [dotenv documentation](https://github.com/bashup/dotenv/).
-
 #### shell-console
 
 The [shell-console](modules/shell-console) module implements a `dk.console` function to provide a `script/console` command that starts a bash subshell with the devkit API and all variables available -- a bit like dropping into a debugger for the `dk` command.  This is particularly handy if you don't have or use `direnv`, as it basically gives you an alternative to typing `script/foo` or `.devkit/dk foo`: within the subshell you can just `dk foo`.
@@ -339,5 +330,4 @@ The following variables control the operation of the container:
 
 Inside the docker container, a `run-bash VERSION command...`  command is run first, allowing you to do any docker-specific setup (e.g. installing additional dependencies) by either overriding the command or defining a `before` handler for the  `run-bash` event.
 
-Note: the docker container will use `.deps/.bash-VERSION` as its `/workdir/.deps`, so that its installed dependencies can be platform-specific.  Running `clean` inside a container will clean only the dependencies for that bash version, while running `clean` outside the container will wipe dependencies for both the base project and all bash versions used to that point.
-
+Note: the docker container will use `.deps/.bash-VERSION` as its `/workdir/.deps`, so that its installed dependencies can be platform-specific.  Running `clean` inside a container will clean only the dependencies for that bash version, while running `clean` outside the container will wipe dependencies for both the base project and all bash versions used to that point.

modules/dotenv

@@ -1,3 +1,16 @@
 #!/usr/bin/env bash
+echo '
+----------------------------------------------------------------------------
+The dotenv module is deprecated!
+
+The `.env` function is now available to .devkit commands by default, without
+using this module.
+
+If your project needs the `dotenv` command or uses it as a build dependency,
+just add `bashup/dotenv` to BUILD_DEPS in your project'"'"'s package.sh.
+
+You can then remove `dotenv` from your `dk use:` list.
+----------------------------------------------------------------------------
+' >&2
+
 require dotenv github bashup/dotenv master dotenv
-source "${BASHER_INSTALL_BIN}"/dotenv

sample.dkrc

@@ -10,7 +10,6 @@
 # -- Shell/Generic Modules --
 # dk use: bash-kit          # enable `with-bash` command to use different bash versions
 # dk use: cram              # run tests using the "cram" functional test tool
-# dk use: dotenv            # manipulate .env files (docker-compose format)
 # dk use: shell-console     # make the "console" command enter a subshell
 
 # -- Watch Modules --

specs/Setup.cram.md

@@ -70,7 +70,7 @@ With git (dirty):
 
     $ git commit -m "Added devkit"
     [master (root-commit) *] Added devkit (glob)
-     13 files changed, 98 insertions(+)
+     13 files changed, 97 insertions(+)
      create mode 100644 .dkrc
      create mode 100644 .envrc
      create mode 100644 .gitignore