Issues with deployment after the service has been down before upgrading account
karlsson2
HOBBYOP

a year ago

Hi!

I recently had my repo be inactive since i forgot to upgrade, got all that sorted but since trying to put the repo up again I have been having continuous issues with it not finding the file it needs.

I have a special deployment command of "node server.js" and as its a monorepo its directed towards my backend folder. 🙂

Solved

11 Replies

karlsson2
HOBBYOP

a year ago

8c169380-53e9-4de5-a5f1-b56cefe00ebb


karlsson2
HOBBYOP

a year ago

There was no issues at all when i deployed the first time, so finding this all very strange 😦


brody
EMPLOYEE

a year ago

hello,

if you click that red highlighted message it will bring you to a docs page that can help here, have you tried that?


karlsson2
HOBBYOP

a year ago

Have tried the information in the docs page, as mentioned I use a monorepo and have directed railway to the specific folder which it seems to find as it lists the contents of said folder.

I just don’t understand what has changed between now and the previous deployment ?


karlsson2
HOBBYOP

a year ago

At the moment it looks like spinning up a new project in railway also works (from my GH repo) so I guess I just need to set everything up again ?


brody
EMPLOYEE

a year ago

glad you where able to get it solved


karlsson2
HOBBYOP

a year ago

That’s not really solving it though if the issue were to happen again and I loose all the information I don’t want to load up an entirely new project 😦


brody
EMPLOYEE

a year ago

the docs page that the red highlighted text links to will help if this ever happens again!


karlsson2
HOBBYOP

a year ago

Which part of the documentation? Because the page that the red highlighted text linked to only referenced the two things I mentioned above.


brody
EMPLOYEE

a year ago


brody
EMPLOYEE

a year ago

!s


Status changed to Solved brody • about 1 year ago


Loading...