2 months ago
Hi Railway!
I have been very excited about discovering the config-as-code railway.json feature that you have implemented. It seems as if I can get most of the way to a full config, but there are a few items that do not seem to square up.
1. Metal Build & Config
In the GUI, I have the option to toggle on "Use Metal Build Environment". After checking the deployment's config settings, I see an item for "buildEnvironment": "V3". Unfortunately, this is not present in the json schema as far as I can tell, and my IDE is flagging this.
> Is 'buildEnvironment' a legitimate option in railway.json? If so, would you please add it to the docs and update the JSON schema to show it?
2. Build Environment vs Runtime Version
As per the above, when we are using the metal build environment, it presents the value as 'V3'. Makes sense, at least as far as I can tell from your blog post.
However, for the deployment options, all I see presented are:
V2
LEGACY
UNSPECIFIED
It is unclear to me what "V2" means in this instance. Is this the V2 that was released in 2023? Naturally, I'd like to use the latest and greatest, especially if it means moving away from the big cloud providers!
> Is "V2" runtime different from the "Railway Metal" and "Railway V3"?
> How can I set my config to use the latest available hardware setting?
Thanks for all of your great work,
Kellan
1 Replies
2 months ago
Heya,
For #1, we do not currently support this in Config as Code. we are in the process of migrating 100% of our builds to our metal builders, and this option will not remain available in the future.
For #2, these are legacy flags that only affected the software managing the containers, and is not a setting for different or better hardware. All of our deploys now go to our own metal infrastructure - I would leave this untouched.
Hope this helps!
Best,
Nico
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved kcerveny • about 2 months ago