зеркало из https://github.com/mozilla/fxa.git
1dd1b038d4
why, after all these years? because there's a few annoying cases where the loopback makes dev harder. When you try to test a flow from a not local machine, like a tv, mobile device, or a saucelabs proxy session. With localhost it's easy enough to forward but loopback not so much enough is enough |
||
|---|---|---|
| .. | ||
| env | ||
| playbooks | ||
| templates | ||
| Makefile | ||
| README.md | ||
| ansible.cfg | ||
| defaults.yml | ||
| hosts | ||
README.md
The command make stack=one23done-stage key=yourkeyname trusted_client_id="dead..." trusted_client_secret="beef..." untrusted_client_id="feed..." untrusted_client_secret="deaf..." will create an EC2+ELB instance [1] with the following attributes:
- builds and runs 123done (https://github.com/mozilla/123done) webserver as both trusted (123done) and untrusted (321done), using the oauth branch
- an AWS ELB serving both port 80, and port 443 traffic with a SSL certificate for *.dev.lcip.org
- registers
123done-stage.dev.lcip.organd321done-stage.dev.lcip.orgin DNS as CNAMES to the ELB - node processes managed by supervisorctl
- ssh access: use
ssh ec2-user@meta-123done-stage.dev.lcip.org; 123done/321done code is under/home/app
[1] assumes you have AWS access keys set up in mozilla's cloudservices-aws-dev IAM, but this ansible code should be not hard to re-use in some other IAM