Wrong PHP version after migrating database
Deployment was working fine, but I migrated the DB to v2.
I get this issue in the Deploy Logs. I don't know where its being set to 3.11.5 or how to set it to anything else. It also seems strange that this wasn't an issue on DB v1 but is now on v2...
16 Replies
Project ID:
97b8f8a8-0a5d-49bb-aa09-983257c5235097b8f8a8-0a5d-49bb-aa09-983257c52350
build logs please https://bookmarklets.up.railway.app/log-downloader/
@Brody
that wasn't with the bookmarklet, but thankfully it tells me every I need to know still
what do you have in your
engines.node in your package.json?yeh wasnt quite sure how to use that
then for future use, just read the 3 steps
"engines": {
"node": ">=12.x.x <=16.x.x",
😂 fair enough
if the issue is related to old node version then that would be handy as I have already updated the project in a seperate repo, but was just testing the migration here first
yeah node 14 is not supported on railway anymore, but there is no clear message so instead you got the most cryptic message of all time about python lmao
so just stick whatever version you run locally here
Lol ok thanks for the info!
Locally it doesn't seem to like changing the node version as lots of things are in compatible. So I'll try the migration on my up to date project and see if that works
which it should as its node v20
then make sure you put 20 in engines.node, that's how railway determines what version of node to use
I have, its just not compatible with other things used in the project. But its fine on Railway
I don't need this old project anymore, so I'm all good!
haha alright sounds good then
Yup! Could do with a better error message I suppose!
for sure