Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

Latest commit

 

History

History
65 lines (43 loc) · 2.38 KB

README.md

File metadata and controls

65 lines (43 loc) · 2.38 KB

Product Advertising API用リバースプロキシ

Build Status Code Climate

What is it?

Amazon Web ServicesのProduct Advertising API用の認証処理を代行するプロキシ(amazon-auth-proxy仕様準拠)の負荷分散を行うリバース・プロキシです。

上記のエンドポイント宛にProduct Advertising API(旧:Amazon アソシエイト Web サービス)のRESTエンドポイント用クエリを付けて送信すると、登録されているプロキシの中からラウンドロビンに選択して要求を中継し、応答を返します。

Install and running on Docker

The docker image is published on docker repositories.

Running rpaproxy in a development environment.

Start a mongodb container. This container is taken from official mongodb image.

$ docker run -d --name mongodb1 mongo

Start the reverse proxy app.

$ docker run --rm -p 80:3000 --link mongodb1:mongodb tdiary/rpaproxy-sinatra

Then, access it via http://localhost in a browser.

Running rpaproxy in a production environment.

In a productino environment, this application requires memcached container to store session data.

You can run rpaproxy with docker-compose.

$ curl -O https://raw.githubusercontent.com/tdiary/rpaproxy-sinatra/master/docker-compose.yml
$ export TWITTER_KEY=your_twitter_key
$ export TWITTER_SECRET=your_twitter_secret
$ docker-compose up

Or, you can also run rpaproxy manually (without docker-compose).

$ export TWITTER_KEY=your_twitter_key
$ export TWITTER_SECRET=your_twitter_secret
$ docker run -d --name mongodb1 mongo
$ docker run -d --name memcached1 memcached
$ docker run --rm -p 80:3000 -e RACK_ENV=production -e MEMCACHE_SERVERS=memcached:11211 -e TWITTER_KEY -e TWITTER_SECRET --link memcached1:memcached --link mongodb1:mongodb tdiary/rpaproxy-sinatra

Building the docker image manually

You can build the docker image manually.

$ git clone [email protected]:tdiary/rpaproxy-sinatra.git
$ docker build -t tdiary/rpaproxy-sinatra .