# Environment Variables

## Overview

By default, each service has different variables, which depends on the environment. For example, database environments, which available on the development environment may differ from the staging environment, and so on... For more information about environments, see the [**Environments**](/getting-started/fundamentals/environments.md) section. Depends on service language, environment variables can be accessed in different ways. 

To access environment variables using **TypeScript** or **JavaScript** language use:

```
process.env
```

{% hint style="info" %}
code.store platform guarantees a high level of security, but we do not recommend displaying secret variables in the stdout or other sources.
{% endhint %}

Below, you can find information about available environment variables which code.store platform set by default.

## Service Environment Variables

`PROJECT_ID` internal ID of the project on the code.store platform

`ENVIRONMENT_ID` name of the [environment](/getting-started/fundamentals/environments.md), where service deployed

`SERVICE_ID` internal ID of the service on the code.store platform

## Database Environment Variables

### Postgres Variables

`DATABASE_HOST` connection host

`DATABASE_PORT` connection port

`DATABASE_NAME` name of the database

`DATABASE_USERNAME` name of the user which can access to services database

### Redis Variables

`REDIS_HOST` Redis connection host

`REDIS_PORT` Redis connection port  

## Language-based environment variables

### TypeScript & JavaScript

`NODE_VERSION` node version, which deployed service used


---

# 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.code.store/getting-started/fundamentals/services/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.