New deploy crashing on pg_dump
I'm attempting to deploy a rails 6 app from GitLab into Railway. It's in api-only mode, and is backed with postgres. It also makes use of a structure.sql instead of the default schema.rb
I keep getting this fatal error after the initial migrate task:
I'm also getting the following error directly below:
What I don't understand is that the initial table migration worked. All my tables have been built out in the postgres service. So the two services are talking to each other.
Do I need to add a build command in the procfile to put pg_dump in the path? Am I missing anything simple?
I'm happy to post the full traces - but they were turning my code blocks into attachments π.
13 Replies
Project ID:
1e4b0651-0174-42a1-aac8-4081f16bb807
1e4b0651-0174-42a1-aac8-4081f16bb807
are these errors coming from the build logs on railway?
They're coming from the deploy logs, but yes, on railway
are you installing pg_dump?
Not intentionally? I presumed it was a postgres extension? That's the impression I got trying to google the errors
haha railway isnt going to magically install pg_dump for you
Right. Thing is, I don't recall installing into my local (though I could have - it was aaages ago that I switched to the schedule.sql)
And I'm not sure how to install things into the environment - in Heroku I could access the dyno directly from my local terminal
So do I do this as a build step?
add a nixpacks.toml to your project with this in it
Oooh, righton. I'll lookup the documentation for nixpacks then. Thanks for your help!
https://nixpacks.com/docs/configuration/file
but for now, just add that file as i have provided
Thanks mate, much appreciated! Gotta get back to the day job (sorry, wasn't expecting a reply straight away π )
haha no problem!