V2 runtime
story-boards-ai
PROOP

2 years ago

In my production backend Servus Settings I see a configuration option for runtime legacy or V2. Currently it's set to legacy.

In my dev service (same GitHub branch) I don't have this option in my settings. Why is that?

What can happen if I switch my production to V2?

Solved

10 Replies

story-boards-ai
PROOP

2 years ago

272cc306-832f-42e6-a34c-9e564719a95d


2 years ago

Runtime V2 introduces a lot of benefits!

You can read more about it here:

https://docs.railway.com/reference/runtime


2 years ago

This change was made a long time ago, was this service of yours been redeployed recently?


2 years ago

You absolutely should be using runtime v2, after you switch to it you can't switch back to legacy


2 years ago

@echoSplice pinging for visiblity


story-boards-ai
PROOP

2 years ago

The production service was running maybe for a year or so. I would have thought the dev service for about the same amount of time. No clue why prod stayed in legacy and dev didn't


story-boards-ai
PROOP

2 years ago

I switched to V2 now. We recently had tons of issues with prod. Last night was the first "normal" night. While we did other things to mitigate things, I think the switch to V2 was key


2 years ago

Yeah the old runtime could be the source of the issues, if anything happens please open another thread


2 years ago

<:salute:1137099685417451530>


2 years ago

!s


Status changed to Solved brody • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...