-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upload media to s3 #3431
base: develop
Are you sure you want to change the base?
upload media to s3 #3431
Conversation
For testing, we could use minio to emulate s3 buckets, if that is an option and/or needed. https://min.io |
@loydbanks thank you for your pull request. Can you work on the two main issues that I found during testing on my machine locally which is adding back in line 19 of config/settings/common.py (PROTOCOL) and figuring out the equivalent of After that is done I will test out the s3 functionality. |
…/loydbanks/3431
All storage classes are subclasses of Storage, which has that function - https://docs.djangoproject.com/en/4.0/ref/files/storage/#django.core.files.storage.Storage.get_available_name I fixed line 19 in config/settings/common.py |
Any background context you want to provide?
When we upload files, we want to send them to s3 to limit storing locally
What's this PR do?
send uploaded files to an s3 bucket
How should this be manually tested?
first make sure you have no docker containers, images or volumes, clear everything.
sudo docker volume create seed_media
sudo docker volume create seed_pgdata
sudo docker-compose up db-postgres db-redis
sudo docker-compose up --build web web-celery
What are the relevant tickets?
#3446
Screenshots (if appropriate)