CLI is not pushing seeders data on railway
I have two seeders to input data into my postgres server on railway.
When I run the seeders, via CLI, It says they ran with no issues and the migrations finished, but there is no data within the required tables:
Solution:Jump to solution
Wasn't a script issue, I solved it.
My config.ts for sequelize was set up in a way that if it fails connection, to default back to development NODE_ENV. It was failing because it was not recognizing postgres.railway.internal for the host....
18 Replies
Project ID:
f3dbe28d-d8b5-4938-9809-d98b1e760b4bf3dbe28d-d8b5-4938-9809-d98b1e760b4b
Command I am running:
how have you verified there isn't any data in the database?
Im on railway dashboard, the tables are empty
the data tab will only show you tables in the default database, you might not be putting data into that database
What do you mean?
When my backend service spins up, and is connected to the postgres instance I made, it creates all the required tables I need via sequelize
I can log into pgAdmin4 to confirm, but im almost positive that the data isnt there, as a logged in user creating a tenant fails because on my backend, its trying to apply global roles to the user during tenant creation.
please check with pgadmin
No data within pgadmin either
so if your data isn't making it into that database, where is it going?
Great question. I only have one database on railway. So why is it telling me that it succeeded in migration for seeders?
that would be more of a question you have to ask yourself, we didn't write the seeder script haha
script works perfectly fine on local postgres server
I would recommend you add better logging to the seeder script, if something is going wrong, why isn't it letting you know?
unfortunately there isn't much we can do here as this isn't necessarily a platform issue
Is there a shell option on the dashboard?
there is not, but this would be an issue with the script, if it isnt doing what its suppoed to it should be telling you whats wrong
Solution
Wasn't a script issue, I solved it.
My config.ts for sequelize was set up in a way that if it fails connection, to default back to development NODE_ENV. It was failing because it was not recognizing postgres.railway.internal for the host.
ah, glad you solved that, partially a script issue, it should surface such errors.