2 years ago
I plan to create a minimal FastAPI application that will have several endpoints for handling files. The main idea is as follows:
-
One of the endpoints will accept a user ID and an image file (e.g., an avatar). This file should be saved in the Volume with a structure like
avatars/{user_id}/{file_name}. -
Another endpoint will accept the user ID and a specific hash, which will be used to locate and return the corresponding file from the same Volume.
-
I plan to use the Volume feature, which provides 5 GB of disk space for storing files. Files, such as user avatars, will be uploaded, stored, and then made available for download or display.
Will this scenario work correctly? I would also like to ask:
- Are there any limitations on read/write operations on the Volume (e.g., in terms of speed or the number of operations)?
- How can I manage stored files (access the Volume) through the Railway interface or CLI?
Or is it better to just write the same minimal application but integrate it with Google Cloud Storage?
0 Replies