Files
vim-ale/dotenv
AJ ONeal 9f28505af7 ref: delete unreachable upstream-fetcher modules
Stacked on the modifications PR. Now that no live code path references
the per-package fetchers, the shared HTTP/parsing helpers, the
in-process normalizer, or the example template, delete them. Pure
deletion — no behavior change.

- ~93 per-package <pkg>/releases.js fetcher modules.
- _common/{brew,fetcher,git-tag,gitea,github,github-source,
  githubish,githubish-source}.js shared HTTP/parsing helpers.
- _webi/normalize.js in-process normalization layer (cache files
  arrive normalized from webicached).
- _example/releases.js fetcher template for new packages.

The Go cache daemon (webicached) is now the sole producer of release
metadata; the Node process never makes an upstream request.
2026-05-08 16:31:59 -06:00
..
2026-03-08 19:38:49 -06:00

title, homepage, tagline
title homepage tagline
dotenv https://github.com/therootcompany/dotenv dotenv: a cross-platform tool to load a .env and run a command.

To update or switch versions, run webi dotenv@stable.

Files

These are the files / directories that are created and/or modified with this install:

~/.config/envman/PATH.env
~/.local/bin/dotenv

Cheat Sheet

dotenv makes it easy to run a command with a set of ENVs (environment variables) from a .env file. It works cross platform, and with any programming environment (Node.js, Go, Rust, Ruby, Python, etc)

# Usage: dotenv [-f .env.alt] -- <command> [arguments]

# Example:
dotenv -f .env -- node server.js --debug

How Precedence Works

  1. command line flags
    • ex: --port 8080
  2. existing environment variables
    • ex: export PORT=8080 or env PORT=8080 mycommand
  3. first-loaded wins for multiple or cascading .env.* files
    • ex: dotenv -f .env,.env.local

ENV syntax

# comments and blank lines are ignored

# you can use quotes of either style
FOO=bar
FOO2="bar2 bar3"
FOO3='bar2 bar3'

# 'export' will be trimmed and ignored
# (yay for bash compatibility)
export FOOBAR=excellent

Why --?

The -- is a common convention for arguments parsers to let them know that everything after the -- should be treated as an argument (a word) rather than a flag (not something like --help).

You should use this whenever one command runs another command.