1391092 - Add ability to serve legacy files from Django (for AWS)

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, enhancement)

Description

[Ryan Johnson (:rjohnson)]

What problem would this feature solve?
======================================
This is helpful for the MDN -> AWS effort. In the current SCL3 deployment, these legacy files are served by Apache. For the AWS effort, at least for the immediate future, we'd like to have Django serve these files.

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

How do you know that the users identified above have this problem?
==================================================================
We're not running Apache or any other HTTP server in front of the Django app in AWS, so we need a way to serve these files.

How are the users identified above solving this problem now?
============================================================
Apache serves the legacy files.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Enable Django to serve these files if configured to do so.

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

Comment 1

[[github robot]]

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

https://github.com/mozilla/kuma/commit/f56a84055154f3ecc84e27879799f32fdc9e5ef4
bug 1391092: add ability to serve legacy files from Django (for AWS)

https://github.com/mozilla/kuma/commit/fd9638ae75495bd9c911de21235fb3b4bbc3307e
bug 1391092: Add comment, cast for SERVE_LEGACY

https://github.com/mozilla/kuma/commit/6fbfea2bdc9ae900c9209af4beebad03407dff6e
Merge pull request #4371 from jwhitlock/legacy-files-2-1391092

bug 1391092: Add ability to serve legacy files from Django

Comment 2

[John Whitlock [:jwhitlock]]

This is not needed in current production, so closing the issue.