Closed Bug 976979 Opened 10 years ago Closed 10 years ago

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

Categories

(Hello (Loop) :: Server, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: alexis+bugs, Assigned: alexis+bugs)

References

Details

Attachments

(1 obsolete file)

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?
Marking as needinfo from bob, jerem and dean as thir op experience could be helpful here.
Blocks: loop_mvp, loop_mlp
No longer blocks: 924922, 907820
Flags: needinfo?(oremj)
Flags: needinfo?(dwilson)
Flags: needinfo?(bobm)
Assignee: nobody → alexis+bugs
https://github.com/mozilla/node-convict looks like a way to deal with these configuration files in a way ops like :)
It's also what we use on Persona, FxA and moz-idp. :)
(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.
Flags: needinfo?(bobm)
Blocks: 977507
Okay, thanks.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(oremj)
Flags: needinfo?(dwilson)
Resolution: --- → FIXED
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/
Status: RESOLVED → VERIFIED
QA Contact: jbonacci
Attachment #8787371 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: