Skip to content
My Beast
Cart
Developer docsMenu

Secrets · Guides

Export a .env

Every environment can be read as a .env: on a page that hides Secret values, or as a download with all of them.

The .env page

An environment's .env tab shows it as a file, grouped by prefix: a Visible line as it is, a Secret one by its name, marked # Secret. Anyone who opens the environment sees it, and nothing on it is recorded.

Copy the 4 Visible lines (or however many there are) takes those lines only, ready to paste.

Download the file

Download .env gives you the file with every value, Secret ones too. It asks first, takes Triage or Admin in the environment, and the download is written in the project's audit log. The file is named after the project and the environment, such as shop-staging.env.

The file holds every value as plain text

Treat it as you would the passwords in it: don't mail it, commit it or leave it in Downloads. A server should pull its environment with a token of its own instead.

What the file holds

The same file a machine gets with mybeast-secrets pull: a first line that says what it is, then a line per variable, sorted by name.

shop-production.env
# MyBeast Secrets · shop/production · change #12 · 4 variables · 27.10.2026 14:05 UTC
APP_NAME='My Shop'
APP_URL=https://shop.example.com
DB_PASSWORD="it's \$ecret"
EMPTY=
  • The first line names the project and the environment, the latest change in it, how many variables there are, and when the file was written, in UTC.
  • A value is written bare when that's safe, otherwise in single quotes. One with a ' or a line break goes in double quotes, with escapes, on one line.
  • Laravel, Docker Compose, Node's dotenv and bash's source all read the same values back from it.

Because of its first line, mybeast-secrets pull will overwrite a downloaded file in its place. See pull.