# Environment Variables

Sensitive information like API keys and tokens are stored inside the `.env` file.

When deploying your application, you should ensure these values are set up in your production  environment and ignore the .env file included with Gravity, as this is for development purposes only. 

Below is a list of the variables used in Gravity. Required variables will be populated for you during the setup process.

```properties
STRIPE_SECRET_API_KEY=
MAILGUN_API_KEY=
CLIENT_URL=http://localhost:3000
WEBSITE_URL=http://localhost:4000
MISSION_CONTROL_CLIENT=http://localhost:5002
TOKEN_SECRET=
CRYPTO_SECRET=
SESSION_SECRET=
SUPPORT_EMAIL=
GENERATE_SOURCEMAP=false
INLINE_RUN_CHUNK=true
FACEBOOK_APP_ID=
FACEBOOK_APP_SECRET=
TWITTER_API_KEY=
TWITTER_API_SECRET=
AWS_ACCESS_KEY=
AWS_SECRET_ACCESS_KEY=
S3_REGION=
S3_BUCKET=
PRODUCTION_DOMAIN=
DB_USER=
DB_PASSWORD=
DB_HOST=
DB_CLIENT=
DB_NAME=
DB_PORT=
ENABLE_API_LOGS=true
STORE_EVENT_LOGS=true
APP_NAME=Gravity
OPENAI_API_KEY=
REDIS_JOB_URL=
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.usegravity.app/gravity-server/environment-variables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.