so you mean, that it is bad to use volume disk to store data? and better to go for storage service like s3?
I think so too, from fly.io doc they recommend me to run 2 machine and 2 storage, to avoid downtime and they ask me to setup the sync between those storage by my own which is not really practical even though I’m fine with the downtime and running it only by 1 machine, it still has problem in my app thus why I make the thread
It is very difficult to give “one size fits all” recommendations in a very concise and clear way. A slightly longer version:
Don’t use volumes unless you are prepared to setup the sync between the volumes.
People who aren’t prepared to set up sync (which, truth be told is most people) use a database, either hosted on fly like Postgres, or hosted elsewhere to address their storage needs.
For those people (which, again, is most people), having only one machine will involve downtime.
I don’t know what time frame you are looking at, but currently in beta is something called litefs, which will store data in sqlite3. I’m working with Kent Dodds on The Epic Stack which supports storing images in litefs on fly.io. If that is of interest to you, I can look into providing an activestorage adapter for sqlite3.
Just be aware that what I described in the paragraph above is either in beta or future work. If this is of interest, I’d be glad to work through this with you.