cookiecutter/cookiecutter-django

Add Digital Ocean spaces as storage option

Open

#1,878 opened on Nov 27, 2018

View on GitHub
 (8 comments) (2 reactions) (0 assignees)Python (10,896 stars) (2,713 forks)batch import
enhancementhacktoberfesthelp wanted

Description

Description

those who do not use AWS s3 but use Digitalocean spaces have trouble deploying static and media, the configurations are a little different.

Solution

AWS_S3_ENDPOINT_URL = env(DJANGO_AWS_S3_ENDPOINT_URL)
AWS_LOCATION = env(DJANGO_AWS_LOCATION)

Contributor guide

Tech stack
python
Domain
backendcloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Django settingsenvironment variables
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requests adding support for DigitalOcean Spaces as a storage backend. The solution involves adding configuration variables for S3 endpoint URL and location in the Django settings (likely base.py or production settings). Look for existing AWS S3 configuration blocks in the cookiecutter django repository and adapt them to support DigitalOcean Spaces via environment variables. Check the issue comments for any additional context or preferred implementation details.