> For the complete documentation index, see [llms.txt](https://developer.gerosense.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.gerosense.ai/gerosense-api-proxy-reference/setting-up-docker-container.md).
# Setting Up Docker Container
To set the Docker container for the API Proxy, you need to provide it with a few environment variables. We highly recommend keeping these variables outside of your version control system.
{% code title="EXAMPLE DOCKER-COMPOSE.YAML" %}
```yaml
services:
gerosense:
image: gerosense/api-proxy:1.3.0
env_file: .env
```
{% endcode %}
Below, is the list of supported environment variables:
| Name | Description |
| ------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| GEROSENSE\_API\_HOST\* | The API host assigned to your account |
| GEROSENSE\_API\_ACCOUNT\* | Your account name |
| GEROSENSE\_API\_ACCOUNT\_PASSWORD\* | Your account password |
| JWT\_SECRET\* | Configuration for the JWT secret used to authenticate your users. See below for details |
| HOST | The host on which `api-proxy` will listen. The default is `0.0.0.0` |
| PORT | The port on which `api-proxy` will listen. The default is `8000` |
## JWT\_SECRET Configuration
`JWT_SECRET` is an JSON object with the following fields:
| Field | Description |
| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| type | The type of your JWT secret. Don't specify it if you use jwk\_url.
For Firebase, don't specify it.
For Supabase, it's HS256.
Supported algorithms: HS256, HS384, HS512, ES256, ES384, RS256, RS384, RS512, PS256, PS384, PS512, EdDSA.
|
| key | Your JWT secret key. Don't specify it if you use jwk\_url.
For Firebase, don't specify it.
For Supabase, you can find it under Settings > API > JWT Secret.
For other providers:
In the case of a symmetric key (i.e., an HMAC-based key), just the key as is. The key must be long enough for the chosen algorithm (e.g., for HS256, it must be at least 32 characters long).
In the case of an asymmetric key (RSA, EdDSA, ECDSA, etc.), only the public key is in a PEM-encoded string or as an X509 certificate.
|
| jwk\_url | JSON Web Key URL.
For Firebase, use:
For Supabse, don't specify it.
|
| audience | One or multiple supported audiences.
For Firebase, use your project ID.
For Supabase, by default, authenticated users have authenticated audience.
Use an array in case you need to support multiple audiences:
\["audience1", "audience2", ...]
|
| issuer\* | Issuer of the token.
For Firebase, use: [https://securetoken.google.com/\<firebase-project-id>](https://securetoken.google.com/\<firebase-project-id>)
For Supabase, use:
https\://\.supabase.co/auth/v1
|
{% code title="EXAMPLE .ENV FOR FIREBASE" %}
```bash
GEROSENSE_API_HOST=https://api-b2b.gerosense.ai
GEROSENSE_API_ACCOUNT=
GEROSENSE_API_ACCOUNT_PASSWORD=
JWT_SECRET='{"jwk_url":"https://www.googleapis.com/service_accounts/v1/jwk/securetoken@system.gserviceaccount.com","audience":"","issuer":"https://securetoken.google.com/"}'
```
{% endcode %}
{% code title="EXAMPLE .ENV FOR SUPABASE" %}
```bash
GEROSENSE_API_HOST=https://api-b2b.gerosense.ai
GEROSENSE_API_ACCOUNT=
GEROSENSE_API_ACCOUNT_PASSWORD=
JWT_SECRET='{"type":"HS256","key":"","audience":"authenticated","issuer":"https://.supabase.co/auth/v1"}'
```
{% endcode %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.gerosense.ai/gerosense-api-proxy-reference/setting-up-docker-container.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.