17 days ago
I've been experimenting with Config-as-Code for a single service of ours called e.g., "api".
It seems incredibly lossy. Half of the time the settings do NOT show that my config-as-code is applied (i.e., the "The value is set in ... .json" message is sometimes there, sometimes not), and worse, when the config-as-code is not applied, the builder is WRONG (nixpacks instead of Docker).
Additionally, I've just pushed and merged an update to the config file and it has not percolated (was actually ignored), and I can't seem to find a way to get the update to resolve in Railway.
Is this expected?
2 Replies
17 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 17 days ago
17 days ago
is the file name not "railway.json" or is not on the root directory? If so, you have to set the filepath explicitly in the service settings section of config-as-code
17 days ago
Which settings are not working consistently? I've noticed that occasionally happens on my build configurations.