3 months ago
Hey team,
Piggybacking on my recent chat with Timo regarding the "zero-config" magic (which is totally awesome).
Right now, working with Buckets feels a bit like walking on a tightrope.
Because there is no versioning, every overwrite is destructive.
Sure, there are workarounds (like manually renaming files to file-v1.txt), but that introduces the exact "config complexity" that Railway tries to eliminate.
If I accidentally overwrite a critical file, it’s game over, data is vaporized instantly. This is serious low-level anxiety material.
I know building a full UI for versioning takes time (and possibly we will have a file explorer soon?), but could we get a simple backend flag to enable versioning on the bucket? Railway magic zero-config style?
Even if we can't see the versions in the dashboard yet, just knowing we can toggle them "on" takes the anxiety away and helps me sleep better.
Best, Bartosz
0 Threads mention this feature
5 Replies
2 months ago
I am using Grist - I need object-versioning!
Without that, I am forced to run a MinIO service and pay for the service infrastructure!
Do let us know when can we expect this feature roll-out!
2 months ago
Also there is a cap on the volume allocation for PRO plan users! So, its like ticking time for me!
2 months ago
If I try to use external storage options like AWS S3, it would result in huge egress cost on the provider!
If I try to use external storage options like AWS S3, it would result in huge egress cost on the provider!
2 months ago
Totally get the frustration with egress fees, it's a budget killer.
Until Railway ships native versioning, check out Cloudflare R2. It’s S3-compatible and has Zero Egress Fees, so you won't get punished for moving data.
Might be the perfect stopgap to keep your infrastructure lean and your wallet safe. Hope this helps! 
2 months ago
I did check it. Like I mentioned, Grist requires the bucket to enable "object-versioning" which is not supported by Cloudflare R2 yet!