Forestadmin-schema.json not updated in production

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


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”


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.


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.


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

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.

1 Like

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 :smiley:

The forest-express code is available here:

And the necessary patch should probably be around here: