<div dir="ltr"><div><div>I'm also interested in this, for <a href="https://github.com/mozilla/fxa-auth-server/blob/master/docs/self-host.docker">https://github.com/mozilla/fxa-auth-server/blob/master/docs/self-host.docker</a> which is used by <a href="https://github.com/michielbdejong/fxa-self-hosting/issues/10">https://github.com/michielbdejong/fxa-self-hosting/issues/10</a><br><br><br></div>Cheers,<br></div>Michiel.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 5, 2016 at 12:37 PM, Nikolaus Thümmel <span dir="ltr"><<a href="mailto:fxacct-ml@ntcomputer.de" target="_blank">fxacct-ml@ntcomputer.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I was recently trying to set up a personal firefox sync + account<br>
server, and wondered how to set up the fxa-auth-server in production<br>
mode. What is the "official" way of doing so? It looks like all npm<br>
scripts are actually enforcing NODE_ENV=dev.<br>
Also, when running in this enforced dev mode, there is a hidden file<br>
test/.env.dev which seems to overwrite some config entries with some<br>
arbitrary values. Why?<br>
<br>
Thank you!<br>
Nikolaus<br>
_______________________________________________<br>
Dev-fxacct mailing list<br>
<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/dev-fxacct</a><br>
</blockquote></div><br></div>