976979 - Loop Server - Find out what best practices are to define production settings

Status: VERIFIED FIXED

(Hello (Loop) :: Server, defect)

Description

[Alexis Metaireau (:alexis)]

We need to find out what's the best way to define production settings when deploying the loop server.

e.g. what do ops use these days: configuration files? environment variables? as we'll be using AWS, what's the best practice here?

Comment 1

[Alexis Metaireau (:alexis)]

Marking as needinfo from bob, jerem and dean as thir op experience could be helpful here.

Comment 2

[Alexis Metaireau (:alexis)]

https://github.com/mozilla/node-convict looks like a way to deal with these configuration files in a way ops like :)

Comment 3

[Benson Wong [:mostlygeek]]

It's also what we use on Persona, FxA and moz-idp. :)

Comment 4

[Bob Micheletto [:bobm]]

(In reply to Alexis Metaireau (:alexis) from comment #1)
> Marking as needinfo from bob, jerem and dean as thir op experience could be
> helpful here.

Configuration files are preferred, because they work well with configuration management systems.  Also, a configuration directory or an include directive that will include everything from a specified directory are helpful.

Comment 5

[Alexis Metaireau (:alexis)]

Okay, thanks.

Comment 6

[James Bonacci [:jbonacci]]

I think this is all covered by work OPs is doing. See the following GitHub repos:
https://github.com/mozilla-services/svcops
https://github.com/mozilla-services/puppet-config/

Comment 7

[Dave Huseby [:huseby]]

Attachment: Bug 976979 - adds privacy.plugin_disabled_barrier.enabled pref

original author: Mike Perry

***
Bug 967979 - Provide a pref to prevent 'This Plugin is Disabled' barrier
original author: Mike Perry

Review commit: https://reviewboard.mozilla.org/r/76156/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/76156/