672238 - Enable Django infrastructure to support site changes without code push

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Wiki pages, defect, P2)

Description

[Les Orchard [:lorchard]]

We can use jsocol's django-waffle [1] and django-constance [2] to implement site switches and variable settings that can be managed from the admin pages without a code push.

Given that infrastructure, we can build content & features whose visibility and functionality are conditional based on admin settings. The catch is that content & features need to be implemented, QA'ed, and pushed to the site before they're needed.

This bug is intended to track the installation and activation of the necessary infrastructure.

[1]: https://github.com/jsocol/django-waffle/
[2]: https://github.com/jezdez/django-constance

Comment 1

[Les Orchard [:lorchard]]

Not included in this bug, BTW, is making Dev Derby content in particular switchable. That'll be another point or so worth of work, but fairly easy to just make a part of the next content push once the groundwork is done

Comment 2

[Luke Crouch [:groovecoder]]

Les, I also noticed that current derby content block is in devderby_landing.html. Is part of this bug to move the current challenge content block up into the tag in __init__.py?

Comment 3

[Les Orchard [:lorchard]]

(In reply to comment #2)
> Les, I also noticed that current derby content block is in
> devderby_landing.html. Is part of this bug to move the current challenge
> content block up into the tag in __init__.py?

No, this bug is just about getting waffle and/or constance working on MDN. File additional bugs for anything beyond that.

Comment 4

[John Karahalis [:openjck]]

It seems Les is making good progress on this, and it could save us time in the future, so I would hesitate to put it off for long.

Comment 5

[John Karahalis [:openjck]]

We'll want to be sure the switches automatically move Derbies into the "Previous" tab after they have ended. See for example bug 675803, which we forgot to file until a day before the 0.9.9 push.

Comment 6

[Les Orchard [:lorchard]]

FWIW, this bug is not about dev derby. This is about getting waffle and/or constance installed. Changes to dev derby require another bug to build on top of waffle or constance. Other parts of the site will be able to take advantage of run-time admin options, as well

Comment 7

[Les Orchard [:lorchard]]

Just filed bug 683919 to be more explicit about next steps required to manage Dev Derby content in particular.

Comment 8

[Les Orchard [:lorchard]]

This went faster than I expected. From a first look, I thought it would need a redis server installed by IT, but it looks like django-constance should work fine with mysql+memcached (which we already have)

https://github.com/mozilla/kuma/commit/868e94bd3d92b1a8038aac84f71a9806b4b26fb4

bug 672238 and bug 683919 - Dynamic config and Dev Derby

* vendor lib update for django-waffle and django-constance
* Remove Dev Derby content selection tags from apps/demos/__init__.py
* Dev Derby constance config defaults added to settings.py
* Grab current challenge, upcoming challenges, previous winner, and
  challenge choices for Dev Derby landing from constance config
* Front and center challenge on Dev Derby landing pulled from current
  challenge tag
* Grab challenge tag choices for Demo Submission form from constance
  config
* Bugfix for pre-checked challenge tag choice on demo submission form
* Bugfix for unicode strings in tag description helpers
* parse_tags utility that preserves user input ordering
* South migration for constance
* Re-enabled ~/vagrant/log/kuma-django.log