# Expanding on ENV variables

**URL:** <https://community.fly.io/t/expanding-on-env-variables/2801>\
**Category:** General\
**Created:** [October 12, 2021, 10:35am UTC](https://community.fly.io/t/expanding-on-env-variables/2801 "2021-10-12T10:35:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danwetherald](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/danwetherald/32/37600_2.png) [@danwetherald](https://community.fly.io/u/danwetherald)\
**Post date:** [October 12, 2021, 10:35am UTC](https://community.fly.io/t/expanding-on-env-variables/2801/1 "2021-10-12T10:35:49Z")

</div>

Looking to expand on the DATABASE\_URL to add db name / schema like so:

> **[Environment variables](https://www.prisma.io/docs/orm/more/development-environment/environment-variables)**
>
> Learn how to use environment variables in your Prisma ORM project

When / Where would be the best place to do so, so that the [deploy] command also has this updated value for migrations.

---

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [October 15, 2021, 1:06am UTC](https://community.fly.io/t/expanding-on-env-variables/2801/2 "2021-10-15T01:06:19Z")

</div>

I think you can just put an `.env` file in your app that includes this:

```auto
DATABASE_URL_WITH_SCHEMA=${DATABASE_URL}?schema=public

```

That .env file support and interpolation seems like a first class feature in Prisma, not something we need to do anything special for.

---

<div class="post-metadata">

**Author:** ![danwetherald](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/danwetherald/32/37600_2.png) [@danwetherald](https://community.fly.io/u/danwetherald)\
**Post date:** [October 15, 2021, 2:00am UTC](https://community.fly.io/t/expanding-on-env-variables/2801/3 "2021-10-15T02:00:31Z")

</div>

Will give this a try and report back!