# Forestadmin-schema.json not updated in production

**URL:** <https://community.forestadmin.com/t/forestadmin-schema-json-not-updated-in-production/479>\
**Category:** Help me!\
**Created:** [June 18, 2020, 4:02pm UTC](https://community.forestadmin.com/t/forestadmin-schema-json-not-updated-in-production/479 "2020-06-18T16:02:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![guillaumejauffret](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumejauffret/32/61_2.png) [@guillaumejauffret](https://community.forestadmin.com/u/guillaumejauffret)\
**Post date:** [June 18, 2020, 4:02pm UTC](https://community.forestadmin.com/t/forestadmin-schema-json-not-updated-in-production/479/1 "2020-06-18T16:02:26Z")

</div>

Hi, I have deployed a new forestadmin-schema.json in production which is not taken into account. I cannot see my new fields on the UI.

## Expected behavior

see the new forestadmin-schema.json through the UI

## Actual behavior

I always see a former forestadmin-schema.json

## Failure Logs

no logs

## Context

Please provide any relevant information about your setup.

- Project Name: joinly-forest

“database\_type”: “MongoDB”,  
“liana”: “forest-express-mongoose”,  
“liana\_version”: “5.7.0”,  
“engine”: “nodejs”,  
“engine\_version”: “12.10.0”,  
“framework”: “express”,  
“framework\_version”: “~4.16.3”,  
“orm\_version”: “5.8.13”

---

<div class="post-metadata">

**Author:** ![guillaumejauffret](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumejauffret/32/61_2.png) [@guillaumejauffret](https://community.forestadmin.com/u/guillaumejauffret)\
**Post date:** [June 19, 2020, 8:49am UTC](https://community.forestadmin.com/t/forestadmin-schema-json-not-updated-in-production/479/2 "2020-06-19T08:49:10Z")

</div>

# Precisions:

I add to precision to understand the problem:

we have a Forest in-app configuration. Our Forest app is inside our Joinly app, at the root level, in a `./joinly-forest/` folder and we run our servers through Docker.

# Behaviour:

Thus, when the command `node ./joinly-forest/server.js` is launched at the **root level** , the Liana is looking for the `forestadmin-schema.json` at the `root level`.

# Fix:

This requires to duplicate and put the `forestadmin-schema.json` at the **root level** of our Joinly app.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/942632c3b2c72408123b872c58b6ae7ceb547c29.png)

# Desirable Solution:

If we prefer keeping the Forest in-app configuration, Forest could make available a **FOREST\_SCHEMA\_PATH** environment variable that tells the Liana where to find the `forestadmin-schema.json` from the **root level**.

---

<div class="post-metadata">

**Author:** ![arnaud](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud/32/32_2.png) [@arnaud](https://community.forestadmin.com/u/arnaud)\
**Post date:** [June 22, 2020, 8:30am UTC](https://community.forestadmin.com/t/forestadmin-schema-json-not-updated-in-production/479/3 "2020-06-22T08:30:37Z")

</div>

Hi @guillaumejauffret,

Let me create an insight in ProductBoard for your feature request.  
As the agents are open source, I think you could contribute with a few lines of code to make this dream come true 😃

The forest-express code is available here:

> **[ForestAdmin/forest-express](https://github.com/ForestAdmin/forest-express)**
>
> 🧱Dependency of Express Lianas for Forest Admin. Contribute to ForestAdmin/forest-express development by creating an account on GitHub.

And the necessary patch should probably be around here:

> <https://github.com/ForestAdmin/forest-express/blob/master/src/index.js#L35>