I know there has been been work on an rpm build script, a cloudformation
config, and puppet-config rules, but haven't tried them myself.
@mostlygeek or @ckolos would be able to comment more.
https://github.com/mozilla-services/svcops/blob/master/services/firefox-accounts/fxa-oauth-server/mock-create.sh
https://github.com/mozilla-services/svcops/blob/master/cloudformations/firefox-accounts/fxa-oauth-server.json
https://github.com/mozilla-services/puppet-config/tree/master/fxa/modules/fxa_oauth
On 06/03/14 19:06, Sean McArthur wrote:
I don't know much about our stage environment. I don't know how
involved deploying to stage is, or who does it. Without a better
understanding, I probably couldn't offer the best option. Thanks for
bring this up, however.
On Tue, Jun 3, 2014 at 4:51 PM, Karl Thiessen <[email protected]
<mailto:[email protected]>> wrote:
After a conversation with ckarlof, I thought I'd ask if anyone has
already thought about this before I start to formulate a plan:
I think we're agreed that having an oauth server and a 123done
instance that talk to the staging env would be a good idea. My
question is, should we deploy them as an extension of what jrgm is
already doing on stage, or perhaps use Danny's whizzy new
stack-builder (which Vlad is happily hacking to accommodate the
two new servers)? There may be other alternatives I haven't
thought of, but those two seem to me to be the most likely candidates.
Do we have proposed names? oauth.stage.mozaws.net
<http://oauth.stage.mozaws.net> and 123done.stage.mozaws.net
<http://123done.stage.mozaws.net> seem reasonable to me.
Is this all already in the planning stages, so I'm fretting for
naught?
Thanks for any context,
--KT.
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
