mozilla / payments-env Goto Github PK

View Code? Open in Web Editor NEW

9.0 12.0 10.0 436 KB

Environment for running payments. See https://payments.readthedocs.org

License: Other

Nginx 3.84% Python 92.66% Shell 3.51%

payments-env's Introduction

This is the main development environment for working on Mozilla payments.

Requirements

Python
Node.js (brew install node on Mac)
Docker (Docker Toolbox for Mac/Windows)

Deployment / QA

The following instructions are for using pre-built containers for deployment or QA purposes.

git clone https://github.com/mozilla/payments-env.git
cd payments-env
docker-compose -f docker-compose-deploy.yml up -d
Find the IP address of your docker system.
- On OS X using boot2docker you can find the address of a container by boot2docker ip
Edit your /etc/hosts file so that the host pay.dev resolves to your IP. For example, you might add this line to /etc/hosts:
```
  192.168.59.103  pay.dev
```
Run docker-compose up -d
Open the example site at http://pay.dev/

Development

Bootstrap your Payments environment by checking out this repository and running the bootstrap.py command. It will automatically check out all other repos into a directory next to your payments-env directory named mozilla-payments, download the appropriate Docker images, and start them.

The only things left will be output at the end of the bootstrap, naming changing your /etc/hosts file to map your Docker's IP to pay.dev and sourcing the created ENV file from your shell for the Braintree Environment variables.

Once you're done, open the example site at http://pay.dev/.

Now you're good to go!

Updating Your Environment

Run ./update-repos.sh to pull the latest version of the master branch on all repos, get new Docker images, and restart all Docker images.

To do this manually, run these commands:

Run git pull in each linked repository (or only in payments-env if you're using pre-built containers).
Run docker-compose stop to make sure all containers are not running.
Run docker-compose pull to get the latest images and rebuild if necessary.
Run docker-compose up -d to start the new containers.

Configurations

There are two docker configurations:

docker-compose.yml is for development purposes and requires the source to be checked out.
docker-compose-deploy.yml is for deployment purposes and contains the application source.

Updating images

If you update the nginx image, run the command build-and-push.sh. This will update the image and push it to docker hub.

CircleCI

Test are run on circle ci for payments-env. We need to figure out how to run them regularly.

payments-env's People

Contributors

Stargazers

Watchers

Forkers

kumar303 muffinresearch jgmize andymckay-limited-access cloudxtreme digideskio sachgits enterstudio

payments-env's Issues

Update Kinto repo/docker hub URL

The Kinto docker image and GitHub repo have moved from mozillaservices to kinto on GitHub and to https://hub.docker.com/r/kinto/kinto-server/ on Docker.

I'm fixing this in my "bootstrap-payments" branch (soon to be posted), but posting here for posterity.

Payments example dies on docker-compose up -d

I see the same thing @andymckay was talking about in irc the other day. Payments-example's container immediately dies on docker-compose up -d and the entire env doesn't appear to be working as a result.

Stand up payments-env somewhere

We need somewhere we can stand up payments-env so we can run tests on it. Could be jenkins, circle-ci or anything really.

Can't be travis because at the moment you can't run docker on travis, without some serious hacks :(

Create a sample/default environment file for development

Instead of getting developers to add a bunch of files to their ~/.profile (or whatever it is on their system/shell), let's provide a file they can activate in their profile.

They would include:

# Include for Mozilla Payments
source ~/Projects/payments-env/development.env

and that file could include:

export BRAINTREE_MERCHANT_ID=tbb7hb44zx28jhsh
export BRAINTREE_PUBLIC_KEY=...
export BRAINTREE_PRIVATE_KEY=...

# etc...

pay.dev.mozaws.net is down

[ec2-user@ip-172-31-37-109 ~]$ source docker--bash: cannot create temp file for here-document: No space left on device
^C
[ec2-user@ip-172-31-37-109 ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1       20G   20G   20K 100% /

Sigh.

Add accept-language rewriting to nginx

To be able to serve a localized version of payments-ui we need to add something to nginx to handle redirects based on accept-language headers.

See http://stackoverflow.com/questions/3657614/how-to-rewrite-location-in-nginx-depending-on-the-client-browsers-language

The benefit with the static route is it should be possible for someone to visit localized static content from the payments-ui tree and see it as it should be. Not to mention if running via pay.dev it should work with accept-language directly.

This looks like it might be worth a try https://github.com/fghibellini/nginx-http-accept-lang/blob/master/lang.lua

If doing it this way is a concern then we should probably look at some other solution e.g. some minimal additional service fronting the SPA.

Got error: Lost connection to MySQL server at 'reading initial communication packet', system error: 104

...in the solitude logs. And login fails.

When I docker-compose stop and docker-compose up -d a second time everything is fine.