Actually load .env in the self-hosted and mail.tm entrypoints

Both setup guides say to copy .env.example to .env and fill it in, but
nothing ever read that file -- Node doesn't load .env automatically, and
neither entrypoint called anything that would. Anyone following the docs
exactly hit "Missing required environment variable" on first run.

Small dependency-free loader instead of pulling in dotenv: doesn't
override a variable already set in the real environment, so
`FOO=bar npm start` still wins over a stale .env value. Verified against
a real .env file end to end, not just typechecked.

Psalm 25 17committed 2 months agoparent 94bfde37a6f7cb5d05be0053eae9b25ce8ba5b480b4b522Browse files