-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Description
Our approach to storage is one of the key unresolved parts of our requirements. The current application uses Azure storage. It also appears to store all media in folders based on the name of the language. The XML the Pi apps retrieves contains file names for the stored media.
The stakeholders have found Azure storage to be expensive. They are open to alternatives.
The structure, with the files stored in folders based on the language, might be a solid requirement or it may not be.
With these questions unresolved, for now we can choose S3 or Azure for our development purposes. If we can manage using Active Storage to keep all the uploaded files in one bucket in line with their requirements, we can go that route. If not, for our immediate purposes we should get storage set up normally and plan to refactor once we have worked out the details with the stakeholders.
See the Media Storage and Integration requirements.
Tasks
- Install and configure Active Storage
- Set up local storage for development
- Configure Azure storage gems and credentials #54
- Add initial content type validations
Metadata
Metadata
Assignees
Labels
Type
Projects
Status