Lumber update do not update ForestAdmin

Help me!
1

Hi, I’m using your service and I updated my db models, but it’s not updated on ForestAdmin dashboard. I deleted old models and use ‘lumber update’ to recreate them, and no changes. Can you help me ? Thanks

2

Hello @John06 and welcome on our community forum ! :slight_smile:

What version of lumber are you currently using ?

3

Hi, I’m using Lumber 4.1.10

4

Do you have a config/database.js file in your repository ?

5

Yes I’ve config/database.js file

6

What are the logs you have on your server side when running this command?

7

It says that the templates are created without any problem, and when I look at the files, the new information is well displayed.

Only Forestadmin is not updated

8

Hello @John06,

If I understand, you already performed these tasks:

  • Delete files under ./models/*.js
  • Run the command lumber update
    • Then you were able to see your new models files under ./models/
  • you expect to see new models content in Forest UI.

Is all that true?
Please note that your server needs to be restarted in order to have changes sent to Forest.

Can you please describe the model fragments that are in the new models but are absent from forest UI? For example, you added a new field, drop a table, etc.

Also please share your project name.

Regards

9

Yes it’s all true ! I restarted the server already !

transactionId: {
  type: DataTypes.STRING,
},

and

isBot: {
  type: DataTypes.BOOLEAN,
  defaultValue: false,
  allowNull: false,
},
10

I received the project name, thanks.

The issue is related to your dev environment, that’s it?

The latest Forest schema receptions I can see were on July 8th and 7th.
They did not trigger a schema change.
In your dev environment, the forest schema date is 23/06/2021 11:18:50. Is it normal from your side?

That may certainly mean your server did not send the schema to Forest after this date.

Can you please:

  • Restart your server again
  • Post here the date of the restart
  • Check the server logs for errors while sending the schema
  • Check api.forestadmin.com is reachable for your server

Regards

11

I restart server `NODE_ENV=production npm run start" at 07/16/21 3:11 PM UTC

I tried to ping api.forestadmin.com and 100% packet loss ! I think it’s the reason!

12

Hi @John06,

I received your IP by private message, thank you.

We do not have any blacklisting features on our side.
As mentioned here, successful communication happened until 8th of July. Maybe you can rely on this date with changes in your infrastructure?

Regards

13

Also, please note that when you have NODE_ENV=production it will not regenerate the schema.
This is the desired behavior: effectively, when in production, the forestadmin-schema.json has to come with the release, and should not be edited directly on production.

Regards

14

I saw that your server is hosted on Heroku, maybe my IP is blacklisted on their side ? Pretty strange that I can’t ping api.forestadmin.com

No I didn’t change anything on my infra

15

Hi @John06,

Did you notice my previous message about NODE_ENV?
It seems to be the source of the problem.

Regards

16

Ok you right ! I ran development env and it’s up to date ! Thanks !