756536 - Django project modernization

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Code Cleanup, defect)

Description

[Les Orchard [:lorchard]]

Webdev has learned some things about Django best practices since devmo and Kuma were started, and they're reflected in Playdoh. It might be nice to do a few things like:

* Revamp the file layout to reflect the new project-module structure of Playdoh - eg. no more apps/ directory, make an mdn module and put the apps under there

* Use the new settings module layout, rather than settings.py / settings_local.py

* Consider using funfactory to replace sumo & devmo apps, upstream any changes or enhancements unique to Kuma

There may be more things. Use this as a blocker bug to spawn workable tasks

Comment 1

[Les Orchard [:lorchard]]

We should clean up the kitsune stuff before revamping the project layout

Comment 2

[Les Orchard [:lorchard]]

Since I was just reminded of this: In a vagrant VM, you can't run tests in /vagrant - it fails with a "no such module vagrant" error. I think that has something to do with the way modules and directories are laid out in the project, and I think playdoh / funfactory fixed that.

Comment 3

[Nickolay_Ponomarev]

> "no such module vagrant"
I filed https://github.com/nose-devs/nose/issues/518 with diagnosis of this issue.

Comment 4

[John Whitlock [:jwhitlock]]

I think we've done most of this work over the last 4 years, such as moving code from apps/ to kuma/. Specific changes should get specific new bugs. For example, the next round of settings changes is bug 1308630.