Railway Deployment Config Issues

I've just deployed a STDB C# (.NET 10 AoT) module to the Railway platform using the steps described in the docs.

THE ISSUE:
I noticed after deployment that the module would not use the volume it created at /stdb and would instead store data in the ephemeral storage of the service.

Due to this, each time I would redeploy the service in Railway, I would loose all my data (Including the module itself).
This would also cause the server to crash since the STDB module is not intended to be stored like this.

THE FIX:
I found that if I:

• Append --data-dir /stdb to the custom start command
• Set the service permission variable (RAILWAY_RUN_UID=0)
  It would then correctly use the /stdb volume attached to the service.

I'm not sure if the docs need to be updated to include these details?

Start with the Railway deployment guide at https://spacetimedb.com/docs/how-to/deploy/railway and compare its custom start command and volume permission instructions with the reported working setup. Done means the guide documents using --data-dir /stdb and setting RAILWAY_RUN_UID=0 so deployments retain module data on the attached volume.