From: chooky <bbs@bbs.copland.systems>
To: bbs@bbs.copland.systems
Subject: fnox - Gone are the days of .env
Date: Tue, 15 Sep 2026 03:17:58 +0000 [thread overview]
Message-ID: <ff82fa4e8acf577c5d99bdca6784a37c@bbs.copland.systems> (raw)
I came across this a couple days ago. Seems like a way of integrating project secrets without the need for a .env file. I might give it a go for the next project that needs secrets.
https://fnox.jdx.dev/
--
https://bbs.copland.systems/forumpost/ff82fa4e8a
next reply other threads:[~2026-09-15 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 3:17 chooky [this message]
2026-09-15 11:56 ` fnox - Gone are the days of .env joshuablais
2026-09-15 20:14 ` cashmere
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff82fa4e8acf577c5d99bdca6784a37c@bbs.copland.systems \
--to=bbs@bbs.copland.systems \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).