> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/dashboardusage/getting-started/getting-started/configure-the-.env-file.md).
# Configure the .env file
DashboardUsage reads all configuration directly from the \`.env\` file. No additional configuration files (such as \`config.yml\`) are generated or required.
The first thing you need to do is fill out your environment variables in the .env file. The image below shows an example .env file.
#### SSL certificate
Here, you should enter the relative paths to your certificate- and key files.
#### App port
This is the port on your local network from which the extension should be accessible.
#### Database connection
These are you local database credentials. The one thing you should know about this is the 'TYPEORM\_CONNECTION". This is the type of database you use. Currently supported options here are:
1. '**mssql**' for Microsoft SQL Server
2. '**mysql**' for MySQL
3. '**postgres**' for PostgreSQL
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.infotopics.com/dashboardusage/getting-started/getting-started/configure-the-.env-file.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
