| # Author: Zameer Ansari | |
| # You should look at the following URL's in order to grasp a solid understanding | |
| # of Nginx configuration files in order to fully unleash the power of Nginx. | |
| # http://wiki.nginx.org/Pitfalls | |
| # http://wiki.nginx.org/QuickStart | |
| # http://wiki.nginx.org/Configuration | |
| # | |
| # Generally, you will want to move this file somewhere, and start with a clean | |
| # file but keep this around for reference. Or just disable in sites-enabled. | |
| # |
| version: '2' | |
| services: | |
| etcd1: | |
| image: quay.io/coreos/etcd:v3.2.5 | |
| restart: always | |
| ports: | |
| - 23791:2379 | |
| - 23801:2380 | |
| volumes: |
You should get an output something like the following
Refresh tokens are used to generate eBay user tokens. User tokens are required for every eBay API call that returns account specific information from eBay. A user token has a life span of about two hours. To avoid forcing your user to log into eBay every time their user token expires, your application instead can store a refresh token. Refresh tokens last about 18 months. The user logs into eBay one time to associate their eBay account with your application. This gives your application permission to act on their behalf. The permission lasts for the lifetime of the refresh token or until the user revokes permission.
To generate a refresh token you need a base64 authorization code, your RuName, and an eBay user willing to give you their login credentials (It can be your account). The steps below would normally be automated
