Environment Variables

When you can't integrate with our command-line utility, or one of our other integrations, you can fall back to using an .env file, or copied environment variables.

Why Environment Variables?

According to The Twelve-Factor App config should be exposed to your applications through the envrionment. This specifically refers to Environment Variables (or env vars).

Keeping config in the environment reduces the liklihood of secrets being checked into source control, and ensures your application's config is sourced from a single location.

Getting started with .env

When you view a project in the Manifold Dashboard, you're presented with a couple of different options for exporting your configuration/secrets.

Copied environment vars

  1. Navigate to your desired project in the Manifold Dashboard
  2. Click Show Credentials below your list of resources
  3. Click Copy to clipboard

If you have a project named api with two resources, and some Stripe configuration, your exported credentials will look like:

## api ##

# logdna-aquatic-bronze-yellow-icosagon
ACCOUNT=29csdkfakekfvb19
KEY=29c3c36redacted5948aca712347

# cloudamqp-vital-champagne-deltoid
CLOUDAMQP_URL=amqp://redacted:the-passphrase@wolverine.rmq.cloudamqp.com/ksbxxbkf

# stripe-secrets
STRIPE_PK=ABCDEFGHIJKLMNOPQRSTUVWXYZ
STRIPE_SK=12345678901234567890

Download an .env file

  1. Navigate to your desired project in the Manifold Dashboard
  2. Click Show Credentials below your list of resources
  3. Click Download .env

A file containing the same output as your copied credentials, will be downloaded automatically.

Your project credentials

An example of the Manifold Dashboard's credential export tool.

Exported credentials