Allow MEDIA_ROOT to be set from the environment

RESOLVED FIXED

Status

Mozilla Developer Network
Setup / Install
--
enhancement
RESOLVED FIXED
4 months ago
4 months ago

People

(Reporter: rjohnson, Assigned: rjohnson)

Tracking

Details

(Whiteboard: [specification][type:feature])

(Assignee)

Description

4 months ago
What problem would this feature solve?
======================================
This aids the AWS work. Currently MEDIA_ROOT is hard-wired to the media folder under the root directory, and in Kubernetes that directory would be ephemeral since it's part of the container. This will allow us to point the MEDIA_ROOT to a location on the shared PVC (EFS).

Who has this problem?
=====================
All visitors to MDN

How do you know that the users identified above have this problem?
==================================================================
This feature helps all users of MDN.

How are the users identified above solving this problem now?
============================================================
It is not currently a problem with MDN in SCL3, only in moving MDN to Kubernetes/AWS.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Allow MEDIA_ROOT to be overridden from the environment.

Is there anything else we should know?
======================================
No.

Comment 1

4 months ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/312c3b428babdaad85c03c74ea1016a5512af957
bug 1388933: allow MEDIA_ROOT to be overridden from the environment

https://github.com/mozilla/kuma/commit/5dbf2ca890088067447fe66d7c200faf4bd466cd
Merge pull request #4359 from escattone/media-root-1388933

bug 1388933: allow MEDIA_ROOT to be overridden from the environment
(Assignee)

Updated

4 months ago
Assignee: nobody → rjohnson
(Assignee)

Updated

4 months ago
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.