a year ago
This happened a few days ago and I finally have time to look at it again. I vaguely recall some automated upgrades happened with the Railway infra, maybe that's related?!
Reporting it here in case you've seen it before and have an easy fix. I'll research further in the meantime.
2 warnings found (use --debug to expand):
- UndefinedVar: Usage of undefined variable '$NIXPACKS_PATH' (line 18)
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 18)ⓘ Deployment information is only viewable by project members and Railway employees.
6 Replies
a year ago
The deployments fail for 3/3 services and one has the new proxy enabled.
a year ago
Hey,
For the linked service - 396857de-3201-4e79-8386-ce492a329840
It looks like the build is failing because lefthook expects it to be a git repo, but the .git folder is not copied over when you run a build.
These are also build failures from 8 days ago, have you tried redeploying?
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Thanks Brody, the last error message in the logs (the one I posted) misled me and I didn't scroll any further up... no comment on that... haha
Issue resolved by removing lefthook install from the prepare NPM script.
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
Great, Looks like all your services are active in that project now, am I good to mark this as solved?
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Yes go for it, thanks for helping me see the obvious in the logs haha
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Awaiting User Response Railway • over 1 year ago
Status changed to Solved brody • over 1 year ago