https://railway.com/project/cdab2de9-2da0-4a87-99ea-3faaf624a45d/service/c464b204-479d-47be-b281-6d362319bc6f/settings?environmentId=ee32fce7-e2a6-4139-83ca-02512d585be2

Since you are auto migrating, should I create all new apps in metal

I'd say it's worth considering for sure, I'm personally creating all my apps on metal to save myself the hassle of having to migrate later

even though I need postgres and redis which are not in metal

You can get redis and postgres on metal, make sure your metal volumes feature flag is enabled in settings

Will there be latency

If your services are in different regions then there will be latency, I used to have my server on us-west metal and my database on us-west GCP and there was about 20ms latency, though I've seen others complain about latency much higher so i guess it depends on your app's setup

You can get redis and postgres on metal, make sure your metal volumes feature flag is enabled in settings

Is it production ready? if now when do you plan to make this GA?

Metal volumes themselves are production ready, the feature flag is just for migrating those volumes

I'm not sure when Railway plans to make it GA

Why is there a feature flag if its ready? I don't understand

Also why do you host your dbs in gcp?

The feature flag is specifically for migrating volumes, not the volumes themselves

You can leave it disabled if you so prefer but then you'd have to create a new redis/postgres (starting on metal by changing default deployment region) and then migrate the data between them manually

I don't host my databases on GCP

Unless you mean to ask whether Railway's hosting their databases on GCP? (to be clear I don't work for Railway)

The feature flag has been removed and it's ~~ not ~~ now* enabled for everyone

now*

yea now 💀 my fault (thanks for the correction)

Currently using Postgres and Redis in Metal.

!s

ah, that makes sense