Files
vim-ale/dotenv
AJ ONeal 23100394ac ref(installerconf): rename config keys and add full URL support
Renames:
- github_repo → github_releases (back-compat kept)
- github_source → github_sources (back-compat kept)
- gitea_repo → gitea_releases (back-compat kept)

New keys:
- gitea_sources, gitlab_releases, gitlab_sources

All keys now accept either owner/repo shorthand or full URLs:
- github_releases = sharkdp/bat
- github_releases = https://github.com/sharkdp/bat
- gitea_releases = https://git.rootprojects.org/root/pathman

Defaults: github → github.com, gitlab → gitlab.com.
Gitea has no default (self-hosted only).

Updated all 73 releases.conf files from github_repo to github_releases.
2026-03-11 11:51:43 -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.