1107729 - [tracker] 12-factor app compliance

Status: RESOLVED FIXED

(Input Graveyard :: Backend, defect, P1)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

At some point in the near future, events will unfold that will change the fundamentals of the Input universe.

In order to coast through these changes unscathed and not trip, fall hard and burn in the fires of infrastructure inferno, it behooves us greatly to adhere to the principles of the 12 Factor App.

This tracker bug covers fixing the things that cause Input to be out of compliance with 12 Factor.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Project plan: https://wiki.mozilla.org/Firefox/Input/12_Factor_App

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Peter said he's going to use decouple for settings (https://github.com/henriquebastos/python-decouple). Definitely worth looking into.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

Putting this in this quarter.

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

Grabbing this since I'm going to work on the sub-bugs.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

For settings, we rolled our own system (it's not hard--there's not much to it) for the time being. Because our current production system continues to use the fjord/settings/local.py methodology and I didn't want to deal with migrating to a new settings system, I did the minimum amount of work to gets environment-variable-based settings working.

In the process of moving Input to AWS, I'd like to revisit settings and redo it probably using django-configurations. That makes it easier to put non-secret settings in version control which makes it easier to make system changes.

Anyhow, I'll update the "move to AWS" bug with this info. This is the only outstanding thing we had at this stage, so I'm closing this out.